Condition logic
  • 16 Feb 2022
  • 1 Minute to read
  • Contributors
  • Dark
  • PDF

Condition logic

  • Dark
  • PDF

The Condition node is used to control task flow based on one or more values. In essence, it functions as an IF statement.
The user can specify multiple separate IF conditions or unite them in sets. Thus, a set of specified conditions will operate as a single IF statement.

If one set of conditions is met, the task will follow the edge from it, and if a different condition is met, it will follow it’s edge. If no conditions are met, the task will follow the default edge.


Key should contain variable's name.

Possible format:

  • parameter_name
  • {{obj.parameter_name}} if there's a need to compose with attached parameter.
    For example:
    • {{temp}} - get "temp" variable value from the task
    • {{main.temp}} - get "temp" variable value from "main" object
    • {{result.SUPPDOCUMENT\.CODE}} - get "SUPPDOCUMENT.CODE" variable value from "result" object

Const may contain:

  • Value which need to be compared with
  • {{value_name}} which need to be compared with

+ Add parameter - button for adding additional condition in current (through "E")

+ Add condition - button for adding new condition

A few conditions in one node are executed as:

IF condition and condition and condition -> transfer
IF condition -> transfer
IF condition and condition -> transfer
Main reasons why the transfer On IF Logic is not working:
  • Register or parameter name is specified incorrectly. Example: parameter in task says “Phone”, in IF Logic it is specified as "phone".
  • Field type in task is specified incorrectly. Example:in task “Count”:10(Int), in block Go If Count=10(String)
  • Attempt to compare two fields content. Example: condotion “amount”==”limt” will not execute, because the system will perceived it as a constant, rather than name ![condition_example]


Was this article helpful?

What's Next