BpmnMultiInstanceLoopCharacteristics
: BpmnMultiInstanceLoopCharacteristics (architecture_autodiagram)
Figure 8 : BpmnMultiInstanceLoopCharacteristics (architecture_autodiagram)
IsSequencialBehaviorLoopCardinalityCompletionConditionBpmnMultiInstanceLoopCharacteristicsBpmnLoopCharacteristicsBpmnDataInputBpmnDataOutputBpmnEventDefinitionBpmnComplexBehaviorDefinition
Attribute
Description
boolean IsSequencial [1..1]
This attribute is a flag that controls whether the Activity instances will execute sequentially or in parallel. If the multi-instance instances are set to be performed in parallel rather than sequential (the isSequential attribute set to false), then the lines of the marker will vertical. If the multi-instance instances are set to be performed in sequence rather than parallel (the isSequential attribute set to true), then the marker will be horizontal
MultiInstanceBehavior Behavior [1..1]
The attribute behavior acts as a shortcut for specifying when events SHALL be thrown from an Activity instance that is about to complete. It can assume values of None, One, All, and Complex, resulting in the following behavior: ? None: the EventDefinition which is associated through the noneEvent association will be thrown for each instance completing; ? One: the EventDefinition referenced through the oneEvent association will be thrown upon the first instance completing; ? All: no Event is ever thrown; a token is produced after completion of all instances ? Complex: the complexBehaviorDefinitions are consulted to determine if and which Events to throw. For the behaviors of none and one, a default SignalEventDefinition will be thrown which automatically carries the current runtime attributes of the MI Activity. Any thrown Events can be caught by boundary Events on the MultiInstance Activity.
string LoopCardinality [1..1]
A numeric Expression that controls the number of Activity instances that will be created. This Expression MUST evaluate to an integer. This MAY be underspecified, meaning that the modeler MAY simply document the condition. In such a case the loop cannot be formally executed. In order to initialize a valid multi-instance, either the loopCardinality Expression or the loopDataInput MUST be specified.
string CompletionCondition [1..1]
This attribute defines a boolean Expression that when evaluated to true, cancels the remaining Activity instances and produces a token.
Association
Description
LoopDataInput : BpmnDataInput [0..1]
LoopDataOutputRef : BpmnDataOutput [0..1]
CompletionEventRef : BpmnEventDefinition [0..1]
The EventDefinition which is thrown when: - behavior is set to one and the first internal Activity instance has completed, - or the behavior is set to none and an internal Activity instance has completed.
ComplexBehaviorDefinition : BpmnComplexBehaviorDefinition [0..*]