These controls solve different problems. Choose the required operator behavior before adding conditions.
Routing: choose the next path
Use Routing when different results lead to different instructions.
Example: a Pass result goes to Accept; a Fail result goes to Record hold. Give each route an explicit condition and require the input used by the decision.
An unconditional route matches when encountered. It is not a special else branch automatically checked last.
Show/Hide: conditionally display a step
Use Logic when an instruction belongs in the sequence but should be shown or hidden for certain cases.
Select a non-branching step and open Logic.
Choose whether the step should be shown or hidden when the condition matches.
Build the condition using values available at that point.
Test a matching and a non-matching case.
For example, show an additional handling instruction when an earlier field identifies a fragile item. Keep the next connection simple.
A Hide rule with no conditions is meaningful: it can hide the step unconditionally. If you want normal display again, clear the display rule rather than leaving an empty Hide configuration.
In this English example, the step is shown when inspectionOutcome equals HOLD. This illustrates Show/Hide; use your own decision value and test both matching and non-matching cases.
Why a control may be disabled
Logic restricts display-expression editing when the step already has a conditional outgoing route or more than one outgoing route.
Conversely, Routing restricts route-condition editing when the source step has a display expression.
Separate the decision from the conditional instruction: branch on a decision step, or use a non-branching instruction with Show/Hide.
Optional: completion is not mandatory
The Process tab contains step flags, including Optional and Milestone. This read-only capture locates these controls; it does not show routing or display conditions.
Use Process → Optional when a step's signature is not required for session completion. Optional is not a display condition and does not itself choose a different route.
Test the result in the intended session. Do not use Optional as a substitute for a Pass/Fail decision.
Milestone: require prior completion
Use Process → Milestone for a step whose completion must be respected when progressing through the path. It is a completion/navigation control, not a display filter or a timer.
Check the interaction with your actual routes and navigation in a test session before relying on it.
Test combinations deliberately
Verify the true and false condition cases, missing data, a skipped earlier branch, and returning to a step after changing a value. Check the visible steps, allowed navigation, and completion result.
For numeric branches, test values just below, exactly on, and just above each boundary.