| ILOG JRules User Guide > Orchestrating Ruleset Execution > Concepts > Rule Overriding |
Rule Overriding |
PREVIOUS NEXT |
Rule overriding is the final stage of rule selection. After all other selection mechanisms, you can specify that certain rules override other rules. Overridden rules are filtered out and not selected for execution.
A rule can override one or more other rules if they are selected in the same rule task at runtime. You can set an entire decision table to override another decision table or tree. You can also combine rule overriding with the hierarchical property, enabling specific rules to override more general rules.
You specify overriding in Rule Studio by setting the overriddenRules rule property. The overriddenRules property enables you to select which rule artifact(s) are to be overridden, and to specify the overriding relationship between a rule and other rules.
The following diagram shows how rule overriding works in a hierarchical rule structure.
Selection operates as follows:
effective date property. This drops rule r2 from the selection, leaving r1, r3, r4, r5, and r6.
p1 has been added the rule task, but p2 has not). This means that r6 is filtered out of the selection.
the location of the rule is over `Florida', so only USA and Florida rules will be considered for execution (see the Geography hierarchy tree in the diagram). This means that r5 is filtered out of the selection.
r3 overrides r1. This leaves only r3 and r4, whose conditions are then evaluated. The rule(s) whose actions match the required conditions are executed.
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |