New Perform vs New Perform action in Behavior context menu #958
Replies: 1 comment
-
Hello,
According to the specification (7.16.6 Perform Action Usages) "A perform action usage is declared as an action usage (see 7.16.2 ) but using the kind keyword perform action instead of just action. A perform action usage is a kind of event occurrence usage (see 7.9.5 ) for which the event occurrence is an action usage, known as the performed action. As for an event occurrence usage, the performed action is related to the perform action usage by a reference subsetting relationship, specified textually using the keyword references or the symbol ::>. Or, if the perform action usage has no such reference subsetting, then the performed action is the perform action usage itself."
Thank you for the feedback, we clearly have improvements to do here. Regards, |
Beta Was this translation helpful? Give feedback.
-
From an Action (in an Action Flow View), the Behavior part of the context menu offers 2 adjacent options: New Perform and New Perform action. The latter makes intuitive sense by creating a new child Action node within the parent Action compartment. The purpose for the former, New Perform, is unclear and provides the user with an overwhelming set of options through a modal Selection Dialog. Of the over 50 selection options available, only 5 were other already-created Action usages. What is the purpose for the New Perform option and what is the source of the ActionUsages that appear? What sort criteria explain the order of this list?



With numerous selection options sharing identical names, how is the user to choose wisely and well?
Beta Was this translation helpful? Give feedback.
All reactions