If i’m not mistaken, you can implement in the explorer a fixed list of actions related to one asset. Sometimes your asset is a table containing rows that have a Lifecycle, with a status column for example. And depending on the status, you dont want to show all actions.
What if you could implement a visibility feature depending on an expression we would be able to build ? So for example, on one action « close » I would make a visibility expression like « status = open ». If status is not open, users would not have the possibility to close as it would be hidden.
Totally makes sense. We've been thinking in the same vein.
Asset commands will evolve in many ways. Conditional command availability is one of them. Other planned improvements:
Unification of "related assets" and general commands
More advanced ways to configure parameters of the called asset in commands - hide (never prompt for) parameters, system-assigned parameters (e.g. user account or role)
Linking a command to another column rather than the one that is being used for parameter assignment (e.g. show the command for column "Name" while do the assignment from the (hidden) column "ID")
Command groups - when a groups of commands are shown in a nested sub-menu
Lineage - finding all assets that use the given asset as a command