The conditions wizard interface is used to set up a specific conditions to execute triggers. in this way you can cover multiple outcomes and build a very responsive workflow.
The upper section of this window will show the condition in verbal form. This way configuring the condition is more intuitive and easy.
Underneath you will find a list of the steps with their input field - sept without inputs will not appear in that list. In the end of the list you will find all the system and the workflow variables beside the variable section.
The conditions are based on the values of those input fields or the values of the system/workflow variables.
The most basic form of a condition will look like:
When Input field is Logical condition
On that you can add an and or a or condition and be more specific
| Logical condition | numerical fields | non-numerical fields |
|---|---|---|
| Equals | v | v |
| Not equals | v | v |
| Is null | v | v |
| Is not null | v | v |
| Includes | x | v |
| Less | v | x |
| Less or equals | v | x |
| Greater than | v | x |
| Greater or equals | v | x |
| Between | v | x |
| Not between | v | x |
Some important notices
| Operator | Behaviour |
|---|---|
| a=b (equals) | Condition succeeds if both operators are empty, |
| a≠b (not equals) | Condition fails if both operators are empty |
| a < b (less than) | Condition fails if one of the operators is empty |
| a < b (greater than) | Condition fails if one of the operators is empty |
| a <= b (less or equal) | Condition fails if one of the operators is empty |
| a >= b(greater or equal) | Condition fails if one of the operators is empty |
| B <= a <= c (between) | Condition fails if one of the operators is empty |
| a < b | |
| Condition passes of operator a is empty |
