Operators and conditions

Conditions allow you to control whether and when something will happen in your application. For example, you can use conditions to control whether a form field is displayed, whether a mapping is used to populate a value automatically, or whether a widget is displayed in a view.

Conditions use operators to define how the condition is applied. By default, a condition checks that one value is the same as (equal to) another value. You can specify other operators to achieve different use cases, such as checking whether one number is larger or smaller than another, or whether a particular value appears in a set of multiple values.

You can use conditions in the following places within your Grexx Platform application:

• Activity logic: Use conditions within If then else or While blocks to control when a trigger or mapping is applied, as well as more advanced options, such as when to throw an error. If the condition is satisfied, the rules in the Then block or While loop are performed. If the condition is not satisfied, the rules in the Else block are performed (if applicable) or the While loop terminates. For more information, see Apply conditional logic to activities.
• Form logic: Use conditions within an If then else block to control whether form actions - such as showing or hiding a field, setting a value, or making a field mandatory - are performed. If the condition is satisfied, the actions in the Then block are performed. If the condition is not satisfied, the actions in the Else block are performed (if applicable). For more information, see Apply conditional logic to forms.
• Datasets: Use conditions to control which items are included in a dataset. Only cases or tasks that satisfy the condition(s) are included in the dataset and are therefore available to display in a view, include in a picklist, or use in a For each loop. For more information, see Configure datasets.
• Static picklist items: Use conditions to filter the static items that are included in a picklist, based on attributes of the current case or a value identified using an inline template (such as an attribute of a related case). Only static items that satisfy the conditions are included in the picklist. For more information, see Picklists.
• Widgets and navigation items: Use conditions to control whether a widget or item in a navigation bar is displayed based on an attribute of the current case or a value identified using an inline template (such as an attribute of a related case). The widget or navigation item is only displayed if the condition is satisfied.
• Activity and navigation item rights: Use conditions to control whether a role is granted rights to perform an activity or access an item in a navigation bar. Rights are only granted to the role if the condition is satisfied.

Tip:

For information about using operators in mappings, see Populate case details automatically.

Standard conditions

A standard condition compares two values, referred to as the "left field" and "right field". By default, a condition checks whether the left and right values are the same (equal to) each other. If the values match, the condition is satisfied (i.e. the condition is true). If the two values do not match the condition is not satisfied (i.e. the condition is false). You can also specify other condition operators to achieve different use cases.

When you create a condition, you must specify the values for the left and right fields. The options available depend on what you're adding the condition to (e.g. activity logic, a dataset, or a picklist). You can use an inline template to retrieve a value from a related case (by linking from an attribute on the current case to another case), use the current date, or specify a date relative to the current date.

Has role conditions

A Has role condition is satisfied (i.e. the condition is true) if the currently logged in user has the specified role.

By selecting the User does not have this role checkbox, you can create a Has not role condition. In this case, the condition is satisfied if the currently logged in user does not have the specified role.

Condition list

By default, when you add multiple conditions, every condition must be satisfied. By grouping conditions into a condition list you can specify whether only one or all of the conditions must be satisfied:

• AND requires all conditions in the list to be satisfied for the result to be true.
• OR requires at least one of the conditions in the list to be satisfied for the result to be true.

You can also implement more complex logic by using multiple condition lists.

Note:

A condition list that does not contain any conditions will be ignored. This means the Then of an If then else block is performed, and the rules in a While loop are performed until the limit is reached.

Condition operators

When adding a condition, specify the operator you want to use to compare the left and right field values.

Name	Operator	Description
Is equal	==	True if the two values are the same.
Is not equal	!==	True if the two values are not the same.
Greater than	>	For use with numerical data. True if the left value is larger than the right value.
Less than	<	For use with numerical data. True if the left value is smaller than the right value.
Greater than or equal to	>=	For use with numerical data. True if the left value is larger than or the same as the right value.
Less than or equal to	<=	For use with numerical data. True if the left value is smaller than or the same as the right value.
In	In	When the right field is a single text (string) value, true if the text in the left field is present in the right field value. For example, "form" in "platform" will return true. When the right field is a multivalue, true if the text in the left field exactly matches one of the values in the right field. For example, "Platform" in ["Welcome", "to", "Grexx", "Platform"] will return true, whereas "form" in ["Welcome", "to", "Grexx", "Platform"] will return false.
Not in	Not in	When the right field is a single text (string) value, true if the text in the left field is not present in the right field value. When the right field is a multivalue, true if the text in the left field does not match any of the values in the right field.
Contains	Contains	When the left field is a single text (string) value, true if the text in the right field is present in the left field value. For example, "platform" contains "form" will return true. When the left field is a multivalue, true if the text in the right field exactly matches one of the values in the left field. For example, ["Welcome", "to", "Grexx", "Platform"] contains "Platform" is true, whereas ["Welcome", "to", "Grexx", "Platform"] contains "form" will return false.
Not contains	Not contains	When the left field is a single text (string) value, true if the text in the right field is not present in the left field value. When the left field is a multivalue, true if the text in the right field does not exactly match any of the values in the left field.
Begins with	Begins with	True if the first N characters of the value in the left field match the value in the right field (where N is the number of characters in the right field). For example, "Grexx" begins with "Gr" will return true. Designed for use with text (i.e. strings); other data types are treated as strings.
Not beginning with	Not begins with	True if the first N characters of the value in the left field do not match the value in the right field (where N is the number of characters in the right field). Designed for use with text (i.e. strings); other data types are treated as strings.
Ends with	Ends with	True if the last N characters of the value in the left field match the value in the right field (where N is the number of characters in the right field). For example, "Grexx" ends with "xx" will return true. Designed for use with text (i.e. strings); other data types are treated as strings.
Not ends with	Not ends with	True if the last N characters of the value in the left field do not match the value in the right field (where N is the number of characters in the right field). Designed for use with text (i.e. strings); other data types are treated as strings.
Any in	Any in	For use with two multivalue sets. True if any of the values in the left (multivalue) field are present in the right (multivalue) field.
Not any in	Not any in	For use with two multivalue sets. True if none of the values in the left (multivalue) field are present in the right (multivalue) field.
All in	All in	For use with two multivalue sets. True if all of the values in the left (multivalue) field are present in the right (multivalue) field.
Not all in	Not all in	For use with two multivalue sets. True if not all of the values in the left (multivalue) field are present in the right (multivalue) field.
Textual equal	Is textual equal (picklist)	Only available for conditions in form logic. Compares the textual value from the picklist item rather than the underlying case ID or static item value.

Note:

The in, contains, begins with, and related operators are not available when adding conditions to form logic.

Null values in conditions

"Null" means that no value has been specified. This is different to "0" (for numerical data) or "false" (for booleans). An empty string ("") is treated as null.

You can use null in conditions. For example, you might use a condition to check whether any text has been entered into a Description field before allowing the user to enter further details or progress to the next tab.

To create a condition that is true if any value has been entered (i.e. "is not null"), specify the relevant field or attribute in the left field, set the operator to Is not equal and set right field type to Value and leave the value field empty. For example, Email address !==.

To create a condition that is true if no value has been entered (i.e. "is null") specify the relevant field or attribute in the left field, set the operator to Is equal and set right field type to Value and leave the value field empty. For example, Due date ==.

When using a greater than or less than operator where one of the values is null, the condition is not satisfied. For example, null < 128, 256 < null, and 512 >= null will all return false. When using the in operator with a multivalue in the right field, note that null in [x, y] will return true and null not in [x, y] will return false.

Note:

There are known issues in form logic when using the in and contains operators with null values, and when working with currency fields. For more information, please contact your Grexx Coach.