When a DataStoreNode accepts an object token, if that token contains an object with the same identity as an object contained in a token already held by the node, then the duplicate object token shall not be placed on the DataStoreNode. Source Unified Modeling Language 2.5.1
When an offer for an object token held by a DataStoreNode is accepted by a downstream object node, the offered token is removed from the DataStoreNode, per the usual CentralBufferNode semantics. However, a copy is made of the removed object token ... Source Unified Modeling Language 2.5.1
The type, ordering, and multiplicity of the argument and result pins of a CallAction shall be the same as the corresponding Parameters. Source Unified Modeling Language 2.5.1
The argument Pins of a CallAction are matched, in order, to the sublist of input Parameters, while the result Pins are matched, in order, to the sublist of output Parameters. Source Unified Modeling Language 2.5.1
Behaviors and Operations have totally ordered lists of owned Parameters, and these Parameters are matched to Pins on a CallAction using that ordering. Source Unified Modeling Language 2.5.1
NOTE. Values of StructuralFeatures may be ordered even if the upper multiplicity is 1. Source Unified Modeling Language 2.5.1
Adding a value to an ordered StructuralFeature requires an insertion point for the new value given in the insertAt InputPin, which is required for ordered StructuralFeatures when isReplaceAll is false and omitted for unordered StructuralFeatures. Source Unified Modeling Language 2.5.1
If isReplaceAll is true ... The StructuralFeature always has a single value when the Action completes, even if the lower multiplicity of the StructuralFeature is greater than 1. Source Unified Modeling Language 2.5.1
If isReplaceAll is true, then the existing values of the StructuralFeature are removed before the new value is added, except if the StructuralFeature already contains the new value, in which case it is not removed under this option. Source Unified Modeling Language 2.5.1
junction – ... If more than one guard evaluates to true, one of these is chosen. The algorithm for making this selection is not defined. Source Unified Modeling Language 2.5.1
NOTE. Such guard Constraints are evaluated before any compound transition containing this Pseudostate is executed, which is why this is referred to as a static conditional branch. Source Unified Modeling Language 2.5.1
a submachine Statemachine can be exited as a result of: reaching its FinalState; triggering of a group Transition originating from a submachine State, or; via any of its exit points. Source Unified Modeling Language 2.5.1
If an AcceptEventAction is used in an Activity, there are special rules for when it is enabled .. Source Unified Modeling Language 2.5.1
