Model Parts, Diagrams, Dictionary Items, and Properties > Dictionary items > Merge node (dictionary item)
Merge node (dictionary item)
For automation interface information about a Merge Node, see Control node (automation interface). For automation interface purposes, a Merge Node is a Control Node that has its Node Type set to Merge Node.
A Merge Node brings together multiple alternate flows. It is not used to synchronize concurrent flows but to accept one among several alternate flows. A Merge Node has multiple incoming flows and a single outgoing flow.
Create a Merge 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 > Merge Node.
• On an Activity Diagram tab, click the Merge 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 Merge Node's notation is as follows.
The View Options on an Activity Diagram allow you to show or hide the Name. In addition, the view options allow you to dock the Merge 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 Merge Node's missing Activity Flows, Comments and Constraints: right-click the Merge Node, point to Populate, and then click the appropriate command.
In the Dictionary pane, Merge Nodes are listed in the UML\Control Nodes folder.
In the Modeler panes, a short-cut symbol on the Merge Node's icon indicates that the item is a stub.
The following sections provide information about how a Merge 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 Merge Node has these properties:
Owned by
Activity
Structured Activity Node —Applies only when the Merge Node is scoped directly to a Structured Activity Node.
Owns
Comment
Constraint
Control Flow —The Control Flow is owned jointly by Merge 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 Merge 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 Merge Node, the IO Flow's other linked item and the IO Flow's IO Item.
Object Flow —The Object Flow is owned jointly by Merge 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 Merge Node can be linked to the following items.
Stereotype —To make a Merge Node valid for a Stereotype, set up Control Node a valid item type.
* 
Creating a merge node
Overview of activity modeling
Was this helpful?