For automation interface information about a Fork State, see
State (automation interface). For automation interface purposes, a Fork State is a State that has its UML State Type set to Fork.
A Fork State splits an incoming transition into two or more transitions terminating on orthogonal target vertices, that is, vertices in different regions of a composite state.
Create a Fork State through a Modeler explorer pane or a State Diagram:
• In a Modeler pane, right-click a State Machine or Sequential State, point to New, point to Pseudo State, and then click Fork State.
• On a State Diagram, click the Fork State toolbar button, and then click the diagram background (within the frame) or within a Sequential State.
When used on a State Diagram, a Fork State's notation is as follows.
The View Options on a State Diagram allow you to show or hide the Name and orientation. By default, the Name is not shown and the orientation is Vertical. See
Fork state view options - state diagram.
On a State Diagram, you can populate Fork States: right-click the State Machine (frame) or Sequential State that owns the Fork States, point to Populate, and then click All States. Note that all owned states are added to the diagram.
In the Dictionary pane, Fork States are listed in the UML\States folder.
In the Modeler panes, a short-cut symbol on the Fork State's icon indicates that the item is a
stub.
The following sections provide information about how a Fork State is used in the model.
Dependency —The Dependency is owned jointly by the Fork State and the other associated item. The access permissions you have to a Dependency are determined by the access permissions of the dependent item.
Transition —The Transition is owned jointly by the Fork State and the other associated item. The access permissions you have to a Transition are determined by the access permissions of the source item.
Fork State toolbar button, and then click the diagram background (within the frame) or within a Sequential State.
on the Fork State's icon indicates that the item is a
stub.
Atomic State (through child State Diagram)
Dependency —The Dependency is owned jointly by the Fork State and the other associated item. The access permissions you have to a Dependency are determined by the access permissions of the dependent item.
Transition —The Transition is owned jointly by the Fork State and the other associated item. The access permissions you have to a Transition are determined by the access permissions of the source item.
Stereotype —To make a Fork State valid for a Stereotype, make State a valid item type.
Sequential State
State Machine
Comment
Constraint
State Model
State Diagram
Variant Diagram