Condition

Overview

The Condition node functions as an "if" statement and enables you to evaluate task parameters and direct the flow of your tasks based on specific requirements set by the user. The Condition node may consist of one or more Condition blocks; each block includes one or more conditions and a single output edge, which leads to the End node. By using multiple Сondition blocks, you can create a nested if/switch-case structure and achieve more flexibility in controlling the task flow based on various conditions.

When a task enters the Condition node, it is evaluated against each condition in the topmost Condition block:

• If the task satisfies every condition in the block, it goes to the End node of the block.
• If the task doesn’t satisfy at least one condition in the block, it goes to the next Condition block.
• If the task doesn’t satisfy all the conditions of any Condition block, it goes to the default End node.

Settings

The Condition node has the following parameters:

1. (Optional) Title and Description: Name and details of the node.

2. Condition block:

   1. Key: Key to specify variables; use curly brackets to enter the key. For example, {{age}}.

   2. Comparison operator: The way the key and the value have to be compared:

      • Equal to (==)
      • Not equal (!=)
      • More than (>)
      • More than or equal to (>=)
      • Less than (<)
      • Less than or equal to(<=)
      • Regular Expression (RegExp)).

   3. Value: Value to compare; use curly brackets to enter the value. For example, {{age}}.

   Note: For more information, go to Parameters and functions.
   3. Type of data:
   * String (S)
   * Number (N)
   * Boolean (B)
   * Array (A)
   * Object (O)

   Note: For more information, go to Data types.

Examples

Adding one Condition block and one condition

In the examples below, we check if the condition is met: whether the value of the age parameter in the task is above 18:

• Condition is met.
  

• Condition is not met.
  

Adding one Condition block with two Conditions

In the examples below, we check whether the two conditions of the Condition block are met:
whether the value of the age parameter in the task is above 18, and the value of the gender parameter is female:

• Both conditions are met.
  

• The first condition is met, but the second one is not.
  

Adding two Condition blocks with one Condition in each

In the example below, the task's parameters are evaluated against two separate Condition blocks. Even though the conditions sets in both blocks are met, the task will only follow the output edge of the top block since it is the first one to be checked against.

Comparing objects in Condition blocks

In the example Process below, we use two Condition nodes in sequence to compare object data type parameters in the following objects with nested parameters: data_obj1, data_obj2 and mod_obj.

First, we define the objects and their parameters in the task.

Then, we send the task to our process. It passes through the first Condition node, where the check is performed for the data_obj1 and data_obj2 objects whether they are identical, and proceeds to the second Condition node. In the second Condition node, the data_obj1 and mod_obj1 are compared. As these objects are different, the task ends up in the final data_obj1 !=mod_obj node.

Error handling & troubleshooting

When working with your Process or State Diagram, you may encounter the following issues.