Conditions

When to use a condition

Use a condition when execution depends on signal data, a variable, a previous step result or another value available in the execution context.

How it works

A condition resolves its operands, applies the selected comparison and returns a Boolean result. The feature using the condition then runs, skips or selects a branch based on that result.

Values

An operand can be a literal value or a value resolved from a path. Type conversion depends on the operator and resolved values.

Common comparisons

• Equality and inequality.
• Numeric ordering.
• Text comparison or matching.
• Boolean state.
• Presence or absence of a value.

Missing data

A missing path does not necessarily equal an empty string, zero or false. Test the condition with representative signal data before using it in a live automation.

Common mistake

Conditions are evaluated when execution reaches them. A value produced by a later step is not yet available.