In a workflow, a business does not always follow a single path. Depending on the situation, you may need to split the workflow into multiple routes. This article explains when to use the three types of split gateways: XOR-Split Gateway, OR-Split Gateway, and AND-Split Gateway.
For details on how to configure transition conditions (routing conditions) and how to branch using a Human Task, see the separate article Specifying Branch Conditions.
What Is Branching?
In most workflows, a series of tasks follows a single path from start to finish. By adding a branching point, you can define multiple possible routes and determine which path to follow based on input data or a user’s selection.
The icon representing the progress of a workflow on the workflow diagram is called a token. Normally, there is only one token, and it proceeds along a single route that satisfies the routing conditions. However, with OR-Split and AND-Split gateways, the token is duplicated so that multiple routes can be processed in parallel.
Quick Reference
If you’re unsure which branching method to use, start with the table below.
| Icon | Branching Method | Token Duplication | Routing Condition | Typical Use | Supported Edition |
 | Human Task branching | No (single path) | User selection or routing condition | The assignee chooses the next route using a button, or the system routes automatically based on input values | Basic or higher |
 | XOR-Split Gateway | No (single path) | Routing condition (first matching route only) | Automatically route to exactly one path based on input values | Basic or higher |
 | OR-Split Gateway | Yes (all matching paths) | Routing condition | Proceed along all routes whose conditions are satisfied | Advanced or higher |
 | AND-Split Gateway | Yes (all paths) | None | Always execute multiple parallel tasks | Advanced or higher |
There are two key questions to consider:
- Do you want the workflow to continue along only one path, or multiple paths?
- Should the routing be determined automatically (using routing conditions) or by a user’s selection?
Because OR-Split and AND-Split gateways duplicate tokens, they are available only in the Advanced Edition or higher.
Branching based on a user’s button selection in a Human Task is explained in the separate article Specifying Branch Conditions.
Gateway Behavior
XOR-Split Gateway (Basic or higher)
A XOR-Split Gateway evaluates the configured routing conditions and automatically sends the token to the first matching path.
No Human Task is created. Instead, the system determines the next route automatically using data that has already been entered.
Use this gateway when the workflow must continue along exactly one of several possible paths.
OR-Split Gateway (Advanced or higher)
A OR-Split Gateway duplicates the token and sends it down every path whose routing condition is satisfied.
Unlike a XOR-Split Gateway, which selects only the first matching path, a OR-Split Gateway proceeds along all matching paths.
Use it when multiple processes should run in parallel, for example:
- Send an email notification while also continuing to the main approval process.
AND-Split Gateway (Advanced or higher)
A AND-Split Gateway does not use routing conditions. Instead, it duplicates the token and sends it down every connected path.
Use it when multiple activities must always be performed in parallel, such as:
- Preparing a contract in the General Affairs department.
- Performing a credit check in the Accounting department.
Notes on Using OR-Split and AND-Split Gateways
Because OR-Split and AND-Split gateways duplicate tokens, there are several design considerations.
- To merge duplicated tokens back into a single flow, use the corresponding OR-Join Gateway or AND-Join Gateway. These gateways wait until all expected tokens have arrived before continuing.
- Alternatively, each branch can end at its own End Event without merging. In this case, the workflow Case is not completed until all tokens have reached an End Event. If an Terminate End Event is used, the Case ends immediately even if tokens remain on other branches.
- Do not use OR-Split or AND-Split gateways inside loops in a way that allows duplicated tokens to be duplicated again. This could result in infinite token generation and is prohibited. Such workflow definitions are rejected as definition errors.
Note: A XOR-Join Gateway is the counterpart of a XOR-Split Gateway. It does not synchronize tokens; each arriving token simply passes through.
Examples
XOR-Split: Approval Request Workflow
In an approval workflow, a XOR-Split Gateway evaluates the amount of an External Payment after approval.
- If the amount exceeds a specified threshold, the workflow proceeds to executive approval
- Otherwise, it automatically continues to the next step
AND-Split: Outsourcing Contract Workflow
In an outsourcing contract workflow, a AND-Split Gateway duplicates the token so that the following activities run in parallel:
- Presenting the draft outsourcing agreement (General Affairs)
- Performing a credit check (Accounting)
After both tasks are completed, they merge at a AND-Join Gateway before the workflow continues.
OR-Split: SLA Request Workflow
In an SLA request workflow, a OR-Split Gateway always proceeds to the Downtime Verification step while also duplicating the token to send an email only when an initial response is required.
This demonstrates how a OR-Split Gateway proceeds along every route whose routing condition is satisfied.
These sample workflows are available for download from the Workflow Apps (Business Templates) library.
