Why would you use conditions?
Conditions allow you to build smart forms and documents by dynamically showing only the relevant questions or clauses depending on the end-user's response.
Conditions are written using a combination of Variables and Operators which define the requirement.
Where can you add conditions?
- Routing (arrows connecting your page blocks)
- Merge, Filter and Loop blocks
- Rule tags in Rich Doc Templates (recommended for automated documents)
- Simple Style Doc Builder
- Forms
- Custom Dashboards
Conditions Syntax
| Field type | Variable Type | Rule | Valid | Invalid |
| All | N/A | Variables should always be to the left of an operator, and requirements to the right | NUM10 > 20 | 20 < NUM10 |
| All | N/A | Operators are not space sensitive | TXT2 == "Orange" AND TXT2=="Orange” are the same |
N/A |
|
Text Inputs, Radio, Dropdown |
String | Inputs are case sensitive and must be wrapped in double quotes. Numbers entered in these field types are also considered Strings and must follow the above rule |
RAD225 == "Yes" (if Radio option is Yes) AND TXT2 > “5" |
RAD225 == "YES" (if Radio option is Yes) AND TXT2 > 5 |
|
Number Inputs,
|
Number | Numbers entered in Number Inputs and Sliders should not be wrapped in quotes as they are not Strings | NUM10 == 20 | NUM10 == "20" |
| Yes/No Inputs | String | Must be wrapped in double quotes and written in caps lock |
ACT5 == "YES" OR ACT5 == “NO” |
ACT5 == YES OR ACT == NO |
| Checkbox | String |
Must be wrapped in double quotes and written in caps lock. The options include “TRUE” or “FALSE” where “TRUE” means the checkbox is checked and “FALSE” meaning unchecked |
CBX101 == "TRUE" OR CBX101 == "FALSE" |
CBX101 == True OR CBX101 == "yes" OR CBX101 ==“True” |
Related Articles