The outgoing ActivityEdges of an InitialNode must all be ControlFlows. The control token placed on an InitialNode is offered concurrently on all outgoing ControlFlows.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
GOTCHA: Just because an InitialNode MAY have more than one outgoing ControlFlow and offers tokens on every outgoing ControlFlow does NOT mean that every outgoing edge takes a control token; InitialNode does NOT act like an implicit fork!
INCORRECT InitialNode no implicit fork
CORRECT InitialNode explicit fork
OPTION double InitialNode
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
SEMANTIC
UML keywords
Activity
InitialNode
ControlNode
control token
ActivityEdge
ActivityNode::outgoing
ActivityNode::incoming
An InitialNode shall not have any incoming ActivityEdges, which means the InitialNodes owned by an Activity will always be enabled when the Activity begins execution and a single control token is placed on each such InitialNode when Activity execution sta
Full quote
The outgoing ActivityEdges of an InitialNode must all be ControlFlows. The control token placed on an InitialNode is offered concurrently on all outgoing ControlFlows.
Next snippet
InitialNodes are an exception to the rule that ControlNodes cannot “hold” tokens, but only manage their flow.
GOTCHA: Just because an InitialNode MAY have more than one outgoing ControlFlow and offers tokens on every outgoing ControlFlow does NOT mean that every outgoing edge takes a control token; InitialNode does NOT act like an implicit fork!
Related snippets
An InitialNode is a ControlNode that acts as a starting point for executing an Activity.
An Activity may have more than one InitialNode.
If an Activity has more than one InitialNode, then invoking the Activity starts multiple concurrent control flows, one for each InitialNode. (Additional concurrent flows may begin at input ActivityParameterNodes and enabled ExecutableNodes ...
An InitialNode shall not have any incoming ActivityEdges, which means the InitialNodes owned by an Activity will always be enabled when the Activity begins execution and a single control token is placed on each such InitialNode when Activity execution sta
When an ExecutableNode completes an execution, the control token representing that execution is removed from the ExecutableNode and control tokens are offered on all outgoing ControlFlows of the ExecutableNode. That is, there is an implicit fork ...
Related snippets (backlinks)
InitialNodes are an exception to the rule that ControlNodes cannot “hold” tokens, but only manage their flow.
Visit also
Visit also (backlinks)