Customization > Automation Interface > Object Attributes and Associations > Control node (automation interface)
Control node (automation interface)
A Control Node is the underlying Modeler Automation Interface object for Activity Final Node, Decision Node, Flow Final Node, Fork Node, Initial Node, Join Node and Merge Node items.
Important: To create a Control Node through the Modeler Automation Interface, you must use the AddByType function. Tell me more...
ATTRIBUTES:
In addition to the common attributes
Description
A textual property that gives an overview of the dictionary item.
Access is read/write.
Is Combine Duplicate
A string that specifies whether tokens having object with the same identity are combined into one by the Control Node. Possible values are TRUE or FALSE.
This attribute applies only when the Control Node is a Join Node, that is, the Node Type is Join Node.
Access is read/write.
Join Spec
A string that specifies the conditions under which the Control Node will emit a token.
By default, the Join Spec value should be 'and'.
This attribute applies only when the Control Node is a Join Node, that is, the Node Type is Join Node.
Access is read/write.
Node Type
A string that specifies whether the Control Node is an Activity Final Node, Decision Node, Flow Final Node, Fork Node, Initial Node, Join Node or Merge Node. Possible values are as follows:
Activity Final Node
Decision Node
Flow Final Node
Fork Node
Initial Node
Join Node
Merge Node
ASSOCIATIONS:
In addition to the common associations
Relationship to Comments that are applied to the Control Node.
Multiplicity is 0+, access is read/write.
Relationship to Constraints that are applied to the Control Node.
Multiplicity is 0+, access is read/write.
A relationship to an Activity that provides input to guard specifications on flows outgoing from the Control Node. In Modeler, this is the Behavior property.
This association applies only when the Control Node is a Decision Node, that is, the Node Type is Decision Node.
Multiplicity is 0-1, access is read/write.
A relationship to the Action Flows for which the Control Node is the destination item.
See also, Outgoing.
Multiplicity is 0+, access is read/write.
A relationship to the Action Flows for which the Control Node is the source item.
See also, Incoming.
Multiplicity is 0+, access is read/write.
Relationship to Comments that are owned by the Control Node.
Multiplicity is 0+, access is read/write.
Relationship to Constraints that are owned by the Control Node.
Multiplicity is 0+, access is read/write.
Owner
A relationship to the Activity or Activity Group (Structured Activity Node) that scopes the Control Node.
Multiplicity is 1, access is read/write.
Owning Activity
A relationship to the Activity for which the Control Node is a child item.
Multiplicity is 1, access is read-only.