Model Parts, Diagrams, Dictionary Items, and Properties > Dictionary items > Fork node (dictionary item)
Fork node (dictionary item)
For automation interface information about a Fork Node, see Control node (automation interface). For automation interface purposes, a Fork Node is a Control Node that has its Node Type set to Fork Node.
A Fork Node splits a flow into multiple concurrent flows. A Fork Node has one incoming flow and multiple outgoing flows.
Create a Fork Node through a Modeler explorer pane or an Activity Diagram:
• In a Modeler pane, right-click an Activity or Structured Activity Node, and select New > Control Node > Fork Node.
• On an Activity Diagram, click the Fork Node button, and then click in free space or inside an Activity Partition, Interruptible Activity Region or Structured Activity Node.
When used on an Activity Diagram, a Fork Node's notation is as follows.
The View Options on an Activity Diagram allow you to show or hide the Name, and orientate the Fork Node vertically or horizontally. In addition, the view options allow you to dock the Fork Node onto the boundary of an Activity Partition. The view options are set through the Control Node entry. See Control node view options - activity diagram.
On an Activity Diagram, you can populate a Fork Node's missing Activity Flows, Comments and Constraints: right-click the Fork Node, point to Populate, and then click the appropriate command.
In the Dictionary pane, Fork Nodes are listed in the UML\Control Nodes folder.
In the Modeler panes, a short-cut symbol on the Fork Node's icon indicates that the item is a stub.
The following sections provide information about how a Fork Node is used in the model. For more information about a property, item, model part or diagram, click it.
Properties
In addition to the standard properties a Fork Node has these properties:
Owned by
Activity
Structured Activity Node — Applies only when the Fork Node is scoped directly to a Structured Activity Node.
Owns
Comment
Constraint
Control Flow — The Control Flow is owned jointly by Fork Node and the associated item. The access permissions you have to a Control Flow are determined by the access permissions you have to its source item.
Dependency — The Dependency is owned jointly by the Fork Node and the other associated item. The access permissions you have to a Dependency are determined by the access permissions of the dependent item.
IO Flow — The IO Flow is owned jointly by the Fork Node, the IO Flow's other linked item and the IO Flow's IO Item.
Object Flow — The Object Flow is owned jointly by Fork Node and the associated item. The access permissions you have to an Object Flow are determined by the access permissions you have to its source item.
Defined in these parts of the model
Activity Model
Shown on these diagrams
Activity Diagram
Variant Diagram
Can be linked to these dictionary items
In addition to the owning Activity or Structured Activity Node, a Fork Node can be linked to the following items.
Stereotype — To make a Fork Node valid for a Stereotype, set up Control Node a valid item type.
*