Skip to navigation
ExtensibilityEvents and NotificationsCondition builder

Condition builder overview

View as Markdown

Describes the UI elements and basic concepts of the condition builder.

The condition builder, a complement to the Java-Expression-Language-based (JEXL-based) approach for defining conditions, enables you to define trigger conditions for custom events or define filter conditions for notification definitions in the Zuora UI in an intuitive and visualized way.

UI elements

The following figure shows the user interface of the condition builder:

UI elements of condition builder

You can find the details of each numbered element in the following table:

Element number

Description

Note

1

The button for adding conditions.

The group-level Add Condition button allows you to add a condition to that specific group.

2

The button for adding groups.

The group-level Add Group button allows you to add a sub-group to that specific group.

3

The field component of a condition.

4

The comparison operator component of a condition.

Available values are as follows:

  • Is equal to
  • Is not equal to
  • Is greater than
  • Is greater than or equal to
  • Is less than
  • Is less than or equal to
  • Starts with
  • In or match
  • Is null
  • Is not null
  • Is empty
  • Is not empty

For more complex operators, switch to Advanced (JEXL) mode.

5

The value component of a condition.

6

The Static toggle that controls the value type.

7

The button for deleting conditions.

8

The logical operator that connects conditions and groups.

Available values are as follows:

  • AND
  • OR

Basic concepts

Condition and group are basic components in the condition builder:

condition structure

Condition

A condition consists of three fields: Field, Operator (comparison operator), and Value. For example:

  • Field: Amount
  • Operator: is greater than
  • Value: 1000.0

Each custom event or notification definition can contain multiple conditions, which must be connected by logical operators (AND or OR).

Operator precedence and group

The evaluation order of conditions is based on operator precedence. The AND operator has higher precedence than the OR operator. To customize the order, you can use groups, which have the highest precedence.

The following is an example:

Conditions

Evaluation order

ConA AND ConB OR ConC

  1. ConA AND ConB → Result
  2. Result OR ConC

ConA AND (ConB OR ConC)

ConB and ConC are grouped.

  1. ConB OR ConC → Result
  2. ConA AND Result

Notes and limitations

  • You can use only one logical operator type (AND or OR) to connect the conditions in a specific group. Use a sub-group to combine the AND and OR operators in a group. For example, ConA AND (ConB OR (ConC AND ConD)) .

  • The Value field is not available if the operator is one of the following:

    • Is null
    • Is not null
    • Is empty
    • Is not empty