Conditions and logic
Answer variables can be used to modify a flow's behavior once they are collected, using conditions. This is useful for making flows dynamic, funneling users into specific tracks, or making a flow more personalized: rather than creating multiple flows for different scenarios, flow questions can be rendered dynamically based on the answers the responder has provided.
Conditions can be used to control many aspects of a flow:
- Enablement - whether or not a feature will be accessible to the flow
If your condition depends on a single answer, it can be defined using our Show conditionally menu -> Add condition.
The simple logic menu
Here you can select an answer variable, set the operator, and choose the value desired.
To learn more about the operators available, see:
If the conditional rendering of your step depends on more than one condition being satisfied, the simple logic editor can accept several arguments using the +Add condition button in the simple logic menu.
The logic between several variables can be configured using either the AND or OR logical operators at one time.
A multi-clause simple logic editor joining several conditions with an AND statement
You can also nest the logic of conditions by grouping (+Add group). This will allow you to set slightly more advanced conditions, such as ensuring one variable condition is satisfied while comparing the value between two other variables.
Variable a is defined, and the logical comparison of variables fruit and is_true needs to be resolved
If you're trying to set more advanced conditions than the simple logic editor allows, you may want to look at using the advanced logic editor, or create a calculated variable.
If the logic you are trying to express involves a combination of multiple different answers, you can use advanced logic to define arbitrary boolean expressions over the answers.
To learn more about advanced logic, see:
For even more complicated conditional logic, define a
Toggling Optional? to "on" allows users to progress past a question without answering it. The default behavior for Formsort flows is to not let users progress in a flow without answering a question.