Summary
The Condition setting lets you control whether a step should run or be skipped when the workflow reaches it. Similar to Gravity Forms field conditional logic, it uses entry values to determine if the step should be executed.
Conditional Logic Type
Perform this step if Any/All of the condition rule(s) match. Will any of the rows of true conditions satisfy the condition so that the step gets executed, or do all of the rows conditions have to be true?
| Setting | Description |
|---|---|
| Logic Type | Choose whether to perform the step if Any or All condition rules match. Determines if one or all rules must evaluate as true. |
| Condition Field/Data | The form field or entry data to evaluate. |
| Condition Operator | Defines how the selected field/data is evaluated (e.g., is, is not, contains, greater than, etc.). |
| Condition Value | The value to compare against. This field adapts based on the selected field and operator (e.g., dropdown list vs. text input). |
If a step is bypassed due to the conditions, it will not appear in the timeline at the bottom of the entry details screen. From the user/workflow perspective, it is as if the step does not exist. However, if an administrator uses the Send to Step feature, that takes precedence over the condition settings defined ,and the step will be executed.
Common Use Cases for Step Conditions
| Use Case | Description |
|---|---|
| Optional steps based on data | Route approvals to different users based on field values. Duplicate steps with varying conditions for each set of assignees. |
| Dynamic assignee routing | Route approvals to different users based on field values. Duplicate steps with different conditions for each set of assignees. |
| Branching logic with Next Step | Combine with the Next Step setting to skip entire step groups. For example, skip design-related steps if “Logo Design” isn’t selected on the form. |
Learn more about setting up branches in your workflow.