Page History
...
- Using a default value expression
- Using a constant value and a business rule
- Using two business rules
- Using a decision table
Default value expression
|
|---|
Constant value combined with business rule
| 
|
|---|
Two business rules
| 
|
|---|
Decision table
|
|---|
| UI Text Box | ||
|---|---|---|
| ||
It is tempting to skip the column for |
...
- Whenever the result depends on multiple input values, it is best to use a decision table.
- Whenever the result is a calculation, it is probably best to use an attribute displayed on a form with a business rule or default expression.
- When using justifications (and you will most likely use them, since they are a best practice), the default value expression has limits; only one justification can be used, regardless of the outcome.
- It is recommended to formally decide which method to use and capture that in an architecture document. A consistent use of a style throughout a project will help the maintainability of a project. There are many roads that lead to Rome, but within one project it is best if all business engineers follow the same road.
...
| Panel | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
Overview
Content Tools