A route condition determines whether a connection can be followed. Conditions belong to the source step's Routing tab.
Add a condition
Select the source step and open Routing.
Add an exit route if needed, then choose its target.
Give the route a useful label, such as Pass or Needs review.
In the condition builder, choose the field or variable.
Choose an operator and provide the comparison value where required.
Add more rules or groups if needed, choosing AND or OR for each group.
Inspect the resulting rule and wait for Saved.
Example: an acceptable voltage range
For a training range of 4.8–5.2 V, configure the Accept route with an AND group:
Output voltage is greater than or equal to 4.8.
Output voltage is less than or equal to 5.2.
Configure the Hold route with an OR group:
Output voltage is less than 4.8.
Output voltage is greater than 5.2.
Test 4.7, 4.8, 5.0, 5.2, and 5.3. The boundary values should take the Accept path.
Available values and operators
The picker includes supported workflow step fields, user variables, system values, and applicable production-entity values. It can list fields from elsewhere in the workflow. Use values that will exist when this decision executes.
Operators depend on the selected type. Numeric comparisons include equals, less/greater comparisons, and ranges. Date, text, Boolean, and kit values have their own choices.
Use the choices shown for that field. Do not expect a regular-expression Matches Pattern option or change-event operators in workflow route conditions.
Route order and empty conditions
An unconditional route: the condition in this capture is empty. This illustrates the empty condition, not the voltage rules in the exercise. The workflow is read-only.
The session follows the first matching connection in its evaluation order. A connection without a condition matches when encountered; it is not automatically deferred until every conditional route fails.
Prefer explicit complementary conditions for branches. Require the decision input, account for all allowed choices, and test what happens with missing or unexpected values.
Show/Hide interaction
If the source step has a display expression, Routing shows a restriction instead of allowing route-condition editing. Put the branch on a separate decision step, or simplify the step to use one mechanism.
See Choose between routing, Show/Hide, Optional, and Milestone for the distinction.