Process Design and Process Studio
Designing a process
Good process design starts from the business process definition, not from the screen. Identify the trigger, the inputs, the happy path, and every realistic exception before drawing. In Process Studio, build a readable main page: one clear left-to-right flow, meaningful stage names, Notes explaining intent, and sub-pages for repeated logic so the main page stays comprehensible.
Master the control stages. A Decision evaluates an expression and takes one of two routes; a Choice handles many named outcomes; a Loop iterates a Collection with a loop counter and a test at the top or bottom; a Block groups stages so a single Recover can handle failures for the whole group. Calculation and Multi-Calculation perform expressions, and Data stages set or reset values.
Traps in questions
- Loops over an empty Collection: the body must not execute. Know whether the test is before or after the first pass.
- Decision expressions must evaluate to true/false; using a text value where a Boolean is expected is a classic distractor.
- Blocks do not stop errors - they only scope where a Recover stage can catch them.
- Sub-pages share the parent's data scope; there is no automatic local variable unless you create one.
- Forgetting that a Process must reach an End stage on every path, including exception paths.
Rule of thumb
Design for the reader: if a reviewer cannot follow the main page in a minute, refactor into sub-pages and rename stages. Then design for the operator: every failure should end in a defined state, not a silent stop.
Worked example
A candidate must loop a Collection of invoices and skip blanks. Correct approach: a Loop stage over the Collection, a Decision testing the invoice number for blank, bypassing the processing sub-page when blank, then continuing the loop. Placing the Decision after the sub-page processes blanks and is wrong.