Operator Precedence

When you add multiple Conditions to your Automation Rules using “And” and “Or”, the order in which you define the condition and the Operator determines how the final result is evaluated. Following rules are applied during evaluation :

1. AND has the higher precedence compared to OR meaning AND conditions are always evaluated first

2. For multiple AND conditions, the evaluation is done from the LEFT moving towards the RIGHT

3. For multiple OR conditions, the evaluation is done from the LEFT moving towards the RIGHT

Below is an example which demonstrates this. It is a single rule but it evaluates to different result based on the field values

The rule involves 2 fields where the field “Impact” should be equal to “High” and the field “Priority” should be either “Blocker” or “Critical”

Scenario 1 :During the evaluation of “Impact = Low” and “Priority = Blocker”, it evaluates to FALSE as below :

Scenario 2: During the evaluation of “Impact = Low” and “Priority = Critical”, it evaluates to TRUE as below, although you may assume it to evaluate to FALSE because Impact is not High:

Conclusion: In such cases, it is always best to split the rule into 2 separate rules.