Switch, and branching honestly

Conditional paths, THE DEFAULT BRANCH PEOPLE FORGET, and what happens to a payload that matches nothing. A switch evaluates conditions in order and takes the first that matches — which is the same first-match behaviour as an approval rule set, and it produces the same defect: a general condition placed above a specific one means the specific branch never executes. Order from most specific to least, and read the switch as the engine reads it. THE DEFAULT BRANCH IS THE ONE PEOPLE FORGET, and its absence is not benign. A payload matching no condition falls through — and depending on the configuration it either ends the flow silently or continues past the switch as though nothing was meant to happen. Either way, the record was not processed and nothing said so. So EVERY switch gets an otherwise branch, and it does something. The three legitimate somethings: raise a fault, if…

In this module: Module 6 · Orchestration patterns

1. 1App-driven versus scheduled
2. 2Invokes, and the shape of a flow
3. 3Switch, and branching honestly
4. 4Loops over collections
5. 5Local variables and assignment
6. 6Sub-integrations and reuse
7. 7Synchronous versus asynchronous
8. 8Stitching in a database or file step
9. 9When an orchestration is too big
10. 10What breaks: three orchestration failures
11. 11Lab briefing · Build a four-step flow