If the outgoing edge of a MergeNode is a ControlFlow, then all incoming edges must be ControlFlows, and, if the outgoing edge is an ObjectFlow, then all incoming edges must be ObjectFlows.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
OR with DecisionNode and MergeNode
SysMLv1: TIP: SysMLv1: Cameo: JoinNode and MergeNode distinguishing notations option
Source
Unified Modeling Language 2.5.1
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
CONSTRAINT
UML keywords
Activity
Activity Diagram
ControlNode
MergeNode
ActivityNode::outgoing
ActivityNode::incoming
ControlFlow
ObjectFlow
A MergeNode shall have exactly one outgoing ActivityEdge but may have multiple incoming ActivityEdges.
Full quote
If the outgoing edge of a MergeNode is a ControlFlow, then all incoming edges must be ControlFlows, and, if the outgoing edge is an ObjectFlow, then all incoming edges must be ObjectFlows.
Next snippet
Related snippets
A MergeNode is a control node that brings together multiple flows without synchronization.
A MergeNode shall have exactly one outgoing ActivityEdge but may have multiple incoming ActivityEdges.
A DecisionNode is a ControlNode that chooses between outgoing ActivityEdges for the routing of tokens.
Related snippets (backlinks)
All tokens offered on the incoming edges of a MergeNode are offered to the outgoing edge. There is no synchronization of flows or joining of tokens.
Visit also
Visit also (backlinks)