Deciding between Conditional Branching and Match Case
Both actions route a process down different paths, but they suit different shapes of decision. Picking the right one keeps your flow readable.
The difference
- Conditional Branching
evaluates a rule and gives you a two-way split: the step goes to
successif the rule holds andfailureif it doesn’t. The rule can combine several conditions (thresholds, presence checks, comparisons). - Match Case compares one value against a list of options and routes to the one branch that matches. Use it when a single value has several distinct outcomes.
Which to use
| Use | When |
|---|---|
| Conditional Branching | The decision is true/false, or depends on combining several conditions. |
| Match Case | One value maps to one of several known outcomes (a status, a type, a category). |
A good signal: if you are about to chain several Conditional Branching steps to test the same value against different possibilities, that is a Match Case.
Examples
- Conditional Branching: approve automatically when an amount is below a threshold; continue only when a status is verified; reroute when a required value is missing.
- Match Case: send a request down a different path for each priority level; handle each document type with its own steps; route by region.
Tip
Two outcomes from a rule means Conditional Branching. Many outcomes from one value means Match Case. When in doubt, model it the way that reads most clearly to someone opening the process later.
Related
- Conditional Branching - the two-way, rule-based split.
- Match Case - one value to one of many named branches.
- Branching & Merging - how paths split and join across a process.
Last updated on