2.8 Comparison Operators: Description and Use in Conditional Tasks.

The system provides several comparison operators that can be used within Conditional Tasks, which are the types of tasks that allow you to perform checks on the fields of the dynamic forms/forms involved within the process.

WARNING! -> the system is “Case Sensitive,” so the same values with different upper or lower case are treated as if they were different.

Example: “VTENEXT” and “vtenext” are seen by the system as different values.

- “equals” -> allows checking whether the contents of a field are equal to a static value specified within the condition. (Figure 1)

Figure 1

PLEASE NOTE: the system does not allow you to compare multiple values at the same time on the same row, so in case you need to perform a multiple check you will have to create separate conditions (Figure 2 and 3)

Figure 2

Figure 3

- “different”->allows to check whether the contents of a field are NOT equal to a static value specified within the condition. (Figure 4)

Figure 4

- “contains” -> allows checking whether the static value specified within the condition is present within a field, regardless of where it is located. (Figure 5)

Taking the example given in Figure 5 as a reference, in case we have a company named “demo_vtenext”, the condition will be verified, since, this tringa contains “vte”.

Figure 5

In contrast to the “equal” operator, the system allows multiple values to be compared simultaneously on the same row (Figure 6)

Figure 6

- “does not contain” -> allows checking whether the static value specified within the condition is NOT present within a field, regardless of where it is located. (Figure 7)

Figure 7

As with the “contains” operator, multiple values can be compared at the same time on the same row (which should be entered separated with a comma).

- “starts for” -> allows you to check whether the contents of a field begin with the static value specified within the condition. (Figure 8)

Figure 8

PLEASE NOTE: the system does not allow you to compare multiple values at the same time on the same row, so in case you need to perform a multiple check you will have to create separate conditions (take Figure 2 and 3 as reference)

- “ends with” ->allows you to check whether the contents of a field ends with the static value specified within the condition. (Figure 9)

Figure 9

PLEASE NOTE: the system does not allow you to compare multiple values at the same time on the same row, so in case you need to perform a multiple check you will have to create separate conditions (take Figure 2 and 3 as reference)

- “has changed to” -> allows you to check whether the contents of the field has precisely changed to the value specified within the condition (Figure 10)

Figure 10

For all those types of fields that might have an undefined value (text, number, date, related to, etc.), by combining the “has changed to” operator with the “different” operator, it is possible to configure a condition to capture a change in the content of a field to a consistent value that you are not aware of. (Figure 11)

Figure 11

The example shown in Figure 11 translates intoto the following sentence,statement: “Expected"The expected closing date has changed to a value I cannot definedefine, but,but at the same time, that value is different fromnot empty, so it will necessarilymust be a consistentvalid value.”"

Starting with version 26.07, the logic for selecting values ​​in Picklist fields has been improved.
Specifically, selectable values ​​are displayed within a multi-select combo box, allowing multiple values ​​to be selected simultaneously.
Additionally, an "Any Value" option has been added, making it easy to include all existing picklist values ​​without having to manually add any new values ​​introduced in the future. (Figure 12)

Figure 12

- “has changed from” -> allows you to check whether the contents of the field has changed from one value to another, both of which are specified within the condition (Figure 12)13)

The first slot should specify the value that the field had before the change, while the second slot should specify the new value that was entered.

Figure 1213

- “greater than” -> allows you to check whether the content of a number/currency field present is greater than an entered static value specified within the condition. (Figure 13)14)

Figure 1314

- “greater than or equal” -> allows checking whether the content of a number/currency field present is greater than or equal to an entered static value specified within the condition. (Figure 14)15)

Figure 1415

- “less than” -> allows you to check whether the content of a number/currency field present is less than an entered static value specified within the condition. (Figure 15)16)

Figure 1516

- “less than or equal” -> allows checking whether the content of a number/currency field present is less than or equal to an entered static value specified within the condition. (Figure 16)17)

Figure 1617

- "in" -> Starting with version 26.07, this operator is available; it allows you to check whether the value in a picklist field matches at least one of the values ​​specified within the condition. (Figure 18)

Figure 18

- "not in" -> Starting with version 26.07, this operator is available; it allows you to verify whether the value in a picklist field does NOT match any of the values ​​specified within the condition. (Figure 19)

Figure 19