Fundamental unit of executable functionality.
The execution of an action represents some transformation or processing in the modeled system, be it a computer system or otherwise. An action may have sets of incoming and outgoing activity edges that specify control flow and data flow to and from other nodes. An action will not begin execution until all of its input conditions are satisfied. The completion of the execution of an action may enable the execution of a set of successor nodes and actions that take their inputs from the outputs of the action. Action can have pre- and post-conditions (using constraints).
: ActivityAction (architecture_autodiagram)
Figure 96 : ActivityAction (architecture_autodiagram)
boolean IsMultipleInstance [1..1]
BPMN: Expresses if several action instances can be run in parallel.
boolean IsCompensation [1..1]
BPMN : Some activities produce complex effects or specific outputs. If the outcome is determined to be undesirable by some specified criteria (such as an order being cancelled), then it will be necessary to "undo" the activities. Compensation activities are activities that "undo" the effect of other activities, in reaction to a compensation event. The Compensation Activity is special in that it does not follow the normal Sequence Flow rules--as mentioned, it is outside the Normal Flow of the Process. This activity cannot have any incoming or outgoing Sequence Flows. The Compensation marker (as is in the Compensation Intermediate Event) will be displayed in the bottom center of the Activity to show this status of the activity.
Output : OutputPin [0..*]
Output pins connected to the Action. The action places its results onto pins in this set.
Input : InputPin [0..*]
Input pins connected to the Action. These are among the total set of inputs.
Handler : ExceptionHandler [0..*]