Page History
This chapter discusses typical design considerations when designing and implementing decisions using Blueriq.
| Table of Contents |
|---|
Setting a
...
binary value
...
When modeling a decision that is limited to a small number of two values (for instance Boolean), there are multiple possibilities to achieve this:
- Using a constant value and a business rule
- Using two business rules
- Using a decision table
...
Constant value combined with business rule
 |  |
|---|
...
Two business rules
|  |
|---|
...
Decision table
 |
|---|
| Info |
|---|
It is tempting to skip the column for male, but it is strongly advised to model a complete table. |
...
It is not a best practice that each decision tables must always contain exactly one result attribute for each possible value. It could be a good starting point in design, but it should not be the ultimate goal to establish one result attribute for each possible value.To illustrate this, the example above has been redesigned to match the before named strategy. In the example above, there are only four discounts: 10%, 20%, 25% and 30%. The decision table holding a result attribute for each value will look like the one below, which in this particular case is not as legible as the two (green) decision tables above:
 |
|---|
...
Expressions in the left column of a decision table
It is possible to use an expression in the left column of a decision table. For instance a count on instances that results in a number that is evaluated.
...
Overview
Content Tools