skip to main content
Corticon Studio: Rule Modeling Guide : Troubleshooting Rulesheets and Ruleflows : Using Corticon Studio to reproduce the behavior : Partial rule firing

Try Corticon Now
Partial rule firing
A Condition/Action rule column might partially fire, meaning Action 1 is executed but Action 2 is not. If Action A cannot execute, then Action B will not execute either, even if there is nothing wrong with Action B by itself. An Action containing any one of the problems listed above is sufficient to prevent a rule from firing, even if all other Actions in the rule are valid.
There are two exceptions to this rule:
Nonconditional actions
In the special Nonconditional rule column, column 0, each Action row in column 0 acts as its own separate, independent rule, so Action row A may fire even if Action row B does not.
Partial execution of rules with relationships and null attributes
When a relationship is null, the rule does not fire. When an attribute is null, and the relationship aspects of the rule can be evaluated, the rule fires partially: The actions related to the association do fire but the action related to a null attribute does not. Consider a Rulesheet and test on the Cargo sample where the Aircraft information is set from its ID, and the total cargo weight computed. If there is no associated Aircraft.flightPlan or Aircraft.flightPlan.cargo in the test, then the rule does not execute (even though those associations are not referenced in the Rulesheet's Conditions section). However, if the associations exist but the attribute Aircraft.flightPlan.cargo.volume is null, the rule does fire partially -- all the Aircraft values are computed but the weight is not computed from the null value of the attribute.