Final rule conflicts

By definition, final rules cannot be overridden. However, two final rules with the same visible key can arise through importing a ZIP file containing rules, or through other uncommon techniques. Such final rules are conflicts.

As a best practice, eliminate final rule conflicts during development, because the rule not marked final is (incorrectly) never executed.

Use the Final Conflicts report, available from a link in the Rule Reports area of the Monitor Activity slice, to find final rules that both have the same name and same other visible key parts. Eliminate any conflicts by deleting one of each conflicting pair until this report is empty.

Decision rule conflicts

A conflict in a decision rule (decision tree, decision table, or map value rule) arises when two elements of the rule form define identical input tests but possibly distinct results.

For example, if two rows of a decision table or map value rule have the same values, only the top row executes at runtime.

Click the  Show Conflicts   button on the form to test for conflicts and mark them with a warning ().

Conflicts are also checked when you save a decision rule form, and when you run the Preflight check.

Conflicts do not prevent the rule from validating or executing, but may indicate that the rule does not implement the intended decision.

	decision table, decision tree, final rule, map value, Preflight tool
	Monitor Activity slice — Reporting on rules About the Application Preflight tool

Definitions — C