When we have multiple event rules, then the binding by last rule must overwrite binding executed by previously running rules. - Known Error

When we have multiple event rules, then the binding by last rule must overwrite binding executed by previously running rules. Description When we have multiple event rules, then the binding by last rule must overwrite binding executed by previously running rules.

Below are the 4 use cases when we have two event rules with expected behaviour: 1. 1st rule is SUCCEEDED to bind - 2nd rule FAILED to bind - The Alert must not be bound 2. 1st rule is SUCCEEDED to bind - 2nd rule SUCCEEDED to bind - The Alert must be bound by 2nd rule 3. 1st rule is FAILED to bind - 2nd rule FAILED to bind - The Alert must not be bound 4. 1st rule is FAILED to bind - 2nd rule SUCCEEDED to bind - The Alert must be bound by 2nd rule

Steps to Reproduce

In below scenario's, alert binding was not overwritten by last rule. Below are the some cases where we observed incorrect behaviour:

1. Event Rule 1 CI Field Matching - Succeeded to bind Event Rule 2 CI Identification - Failed to bind Expected: Alert is NOT bound Current: Alert bound by 1-st rule

2. Event Rule 1 CI Identification - Succeeded to bind Event Rule 2 CI Field Matching - Succeeded to bind Expected: Alert bound by 2nd rule Current: Alert bound by 1-st rule

3. Event Rule 1 CI Identification - Succeeded to bind Event Rule 2 CI Field Matching - Failed to bind Expected: Alert is NOT bound Current: Alert bound by 1-st rule

Workaround This problem has no workaround, is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.