Image Removed This chapter discusses typical design considerations when designing and implementing a decision with a limited number of possible outcomes using Blueriq.
...
- Using a default value expression
- Using a constant value and a business rule
- Using two business rules
- Using a decision table
Default value expression
| Info |
|---|
|
 Image Modified
|
Constant value combined with business rule
| Info |
|---|
|
 Image Modified
|  Image Modified
|
|
Two business rules
| Info |
|---|
|
 Image Modified
|  Image Modified
|
|
Decision table
 Image Removed
|
|---|
|
Image Added |
| Info |
|---|
| UI Text Box |
|---|
type | note |
|---|
It is tempting to skip the column for Male, but it is advised to model a comprehensible table. In most cases, comprehensibility implies completeness (the mere fact that Male is missing from a gender-table might cause suspicion). |
| UI Text Box |
|---|
type | note
| Info |
|---|
It is perhaps even more tempting to skip the [ ]-column for ELSE, but it is also advised to model an ELSE-column whenever the values are not restricted by a value list. If Applicant.Gender was in fact limited by a value list consisting of the values Male and Female and it is obvious the set will never expend, the ELSE-column would have been redundant. |
...