Working with conditions

Once you understand Working with Process maps, you can add conditions to processes. Note a condition can have multiple options to check. Read How to have a condition with multiple options.

1. Add a Decision

Once on a process map:

1. Click on the {{buttons:processes/add}} top right
2. The following popup will appear: {{popups:decisions/add}}
3. Select "Decision". The popup will change and look as follow: {{popups:decisions/add}}
4. Complete the form
5. For each condition you want to add, click on the " Condition" button.
   {{>key-operator-value-band}}
6. Fill in the condition using variables (read Working with variables in RPAs), the operator and the value.
7. The operator works as follow:
   1. >= (bigger than or equal to) - If the variable is bigger than or equal to the specified value, the condition will return TRUE, else FALSE. Only works with numbers
   2. > (bigger than) - If the variable is bigger than the specified value, the condition will return TRUE, else FALSE. Only works with numbers
   3. <= (smaller than or equal to) - If the variable is smaller than or equal to the specified value, the condition will return TRUE, else FALSE. Only works with numbers
   4. < (smaller than) - If the variable is smaller than the specified value, the condition will return TRUE, else FALSE. Only works with numbers
   5. = (equal to) - If the variable is equal to the specified value, the condition will return TRUE, else FALSE. Only works with numbers
   6. != (not equal to) - If the variable is not equal to the specified value, the condition will return TRUE, else FALSE. Only works with numbers
   7. Contains - If the variable contains the specified value, the condition will return TRUE, else FALSE. Only works with text
8. Click "Add" once you are done.

Another way to insert a condition in your process, is to copy another activity and then to edit it. Read Working with Process maps to understand how to edit a process activity.

2. Connect the decision to the process

Once you have added the decision to the process, it may not be in the correct position on the process map, or may not be connected to the correct activities. You can drag the decision to where it should be in the process, and then connect it to the appropriate activities. For more on how to do this, read Working with Process maps.

Note that there should be at least 2 connections "exiting" the condition.

3. Set the connection labels (optional)

Once the decision is created and in the correct position within the process, it is important to indicate which activities will follow next if:

1. The condition is met (TRUE)
2. The condition is not met (FALSE)

Having said this, it is important to first note that there are at least two connections coming from the condition, to two different activities. Once you have confirmed it contains at least two "exiting" connections:

1. Click on the first connection. The popup will show: {{popups:activities/labels}}
2. Select the type of connection. If this connection should be the "TRUE" part, then leave it as is (DEFAULT / TRUE). Otherwise change it to FALSE.
3. Optionally, enter the label "name". This allows you to give it as much meaning and make the process as readable as possible. Give it a name such as Yes and No respectively, or True and False.
4. If it is an RPA process, you can also specify how long the bot needs to wait before going onto the next activity, and the condition for waiting (At least, At most, or Exactly).
5. Click "Add" once you are done.
6. Do the same for the other connection.

4. The full list of operators

A condition compares a variable against a value using an operator. The same operators are available when you filter a loop or a trigger.

• = / != – equal to / not equal to.
• >, >=, <, <= – greater than / less than (and or-equal-to). For numbers.
• between – the value falls within a range (numbers or dates).
• contains – the text includes the value.
• in – the value is one of a list of options.
• starts with / ends with – the text begins or ends with the value.
• matches – the text matches a regular expression (regex), for advanced pattern checks.
• is empty – the variable has no value.
• similar – the text is approximately the same (a fuzzy match), useful when spelling or spacing may vary.

Most operators also have a negated form (for example "does not contain", "does not start with", "is not empty"), so you can express the opposite without rearranging your TRUE/FALSE branches.