skip to main content
Corticon Studio: Rule Modeling Guide : Rule writing techniques and logical equivalents : Qualifying rules with ranges and lists : Using ranges and value sets in condition cells : Alternatives to value ranges

Try Corticon Now
Alternatives to value ranges
As you might expect, there is another way to express a rule which contains a range of values. One alternative is to use a series of Boolean Conditions that cover the ranges of concern. This is illustrated in the following figure:
Figure 97. Rulesheet Using Boolean Conditions to Express Value Ranges
The rules here are identical to the rules in Rulesheet Using Value Ranges in the Column Cells of a Condition Row and Rulesheet Using Open-Ended Value Ranges in Condition Cells, but are expressed using a series of three Boolean Conditions. Recall that in a decision table, values aligned vertically in the same column represent AND 'ed Conditions in the rule. So rule 1, as expressed in column 1, reads:
Expressing this rule in friendlier, more natural English, we might say:
This is how the rule is expressed in the Rule Statements section in Rulesheet Using Boolean Conditions to Express Value Ranges. The same rules may also be expressed using a series of Rulesheets with the applicable range of flightNumber values constrained by Filters. Corticon Studio gives you the flexibility to express and organize your rules any number of possible ways – as long as the rules are logically equivalent, they will produce identical results when executed.
In the case of rules involving numeric value ranges as opposed to discrete numeric values, the value range option allows you to express your rules in a very simple and elegant way. It is especially useful when dealing with Decimal type values.