Alternatives to value ranges
- Last Updated: June 9, 2021
- 2 minute read
- Corticon
- Version 7.2
- Documentation
As you might expect, there is another way to express a rule that contains a range of values. One alternative is to use a series of Boolean conditions that cover the ranges of concern, as illustrated:
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 conditions that use the AND operator. So rule 1, as expressed in column 1, reads:
![]()
The following expresses this rule in friendlier, more natural English:
![]()
This is how the rule is expressed in the Rule
Statements section in the preceding figure, Rulesheet
Using Boolean Conditions to Express Value Ranges. The same rules can 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
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 simple and elegant way. It is especially useful when dealing with decimal type values.