What is a Branch?
A branch allows you to create an alternative path within a process. When you reach a fork in the road, you can choose different directions, splitting the process into multiple steps that follow separate paths. This enables you to design processes with more complexity, where tasks can take different routes depending on the chosen path.
Branching is not automatically enabled. Administrators can allow branching in a company by following these instructions.
To create a branch, select the orange plus icon that appear when hovering at the bottom of a node.
When a branch is created, the child nodes will always be added below the parent node.
Create a Branch with an Existing Node
Edit the node (activity, decision, process link, event)
Select the node and press ENTER
Double-click
Right click and select edit
In the diagram content menu, click on the cog and select 'update'
Change to the Connectors tab
Select a parent node (the node that will appear above the node you are editing)
Select the line positions (where you want the connectors to enter and exit)
Click the 'Update' button.
Once a node has a child, the child node will appear in the drop down as the parent node option. This allows users to only select 1 child node for every parent.
Create a Branches with a New Node
Easiest method: Hover over the bottom of the node where the branch will be added and select the orange plus icon:
OR
Add a new node (activity, decision, process link, event)
Change to the Connectors tab
Select a parent node (the node that will appear above the node you are editing)
Select the line positions (where you want the connectors to enter and exit)
Click on Add Activity
Add An Endpoint
An endpoint can be added to a branch. Any node within a branch can have an endpoint, it is up to the user to correctly set the endpoint.
Note:
Branches cannot be formed within gateways, i.e., you cannot have a branch in a gateway.
All nodes (except decisions) within a branch will have their assigned role included in the node (embedded). They may appear to fall under the incorrect swimlane, but the role can be seen within the node to clearly identify who is responsible. All role assignments can still be seen on the diagram content menu.