Configure feature action on feature detail only

Répondu

Permanently deleted user

7 juillet 2022 10:13

Hi, 

 

For a use case we would like to configure a feature action on certain layers only. This workflow should only be accessible on the feature detail level, and not on the collection of features selected. 

 

Say, for example, I made a selection of 5 objects in the map. Then I want the action to be available when I open the feature details of 1 of these objects, and not on a higher level.

 

I can achieve this by manually configuring the context menus for the results-components, but then the action is available for all layers, where I just want to have it available for certain layers.

 

Is there a way to achieve this?

 

Thanks!

2

• 

  Nico Burgerhart

  7 juillet 2022 10:20

  Hello @...

  You can configure a feature action for a specific layer. Is this what you want?

  https://docs.vertigisstudio.com/webviewer/latest/admin-help/Content/gwv/settings-map.htm?tocpath=Configuration%7CComponent%20Settings%7C_____19#map-feature-actions

  0
• 

  Permanently deleted user

  7 juillet 2022 12:02

  Hi Nico, 

   

  Thanks for your answer. Unfortunately, it is not what I'm looking for.

  When configuring a feature action on a layer, this feature action is available for an individual feature, as well as for a group of selected features from this layer.

   

  What we want to achieve, is the following:

  1. The feature action should be available to features only of specific layers

  2. The feature action should only be available on individual features. In other words: only when viewing the feature details, and not from the results list for  a group of said features.

   

  We've managed to find ways to achieve either one of these goals, but not both.

  0
• 

  Cam Barnard

  29 juillet 2022 18:21

  Hi Nino - in general I can't think of a simple way to do this. If a feature action is configured for a feature, it will generally show up in both the 'single feature' views (like result details) and the 'multi feature' views like the group of features. We did recently create some extension points so that you can write you own custom canExecute logic in Arcade script. I suspect that with this you could configure your own canExecute script that looks at how many feature there are and if that is != 1 then you wouldn't see that command. This sounds like what you are looking for but I don't have a ready example.

  0
• 

  Permanently deleted user

  1 août 2022 06:42

  Hi Cam,

   

  Thank you for your reply. This does sound like a workable solution. I will look into it and give it a try. 

   

  Thank you,

   

  Nino

  0
• 

  Chelsea Rozek

  7 mars 2024 16:21

  Hi @... , did you figure out a way of doing this?

  0
• 

  Davood Kazemi

  6 mai 2024 05:42

  Hey Cam Barnard 

  I'm interested in this topic as well. if you can provide some example of how we can utilize Arcade.Run commad in this scenario would be great,

  0
• 

  Heather Widlund

  20 septembre 2024 18:07

  Chelsea Rozek Davood Kazemi I found an example of using the Arcade.Run code to limit feature actions to single features in this thread which worked for me.

  0

Vous devez vous connecter pour laisser un commentaire.