In the Project Explorer view, expand the rules composer DC node, the Rules Modeling node, and double-click the ruleset node.
In the Outline view , choose the decision table node.
In the Decision Table Editor, expand the decision table, under the Header section, you can set the following properties to true or false for a decision table:
If this property is set to true, the engine tries to evaluate more than one condition row of a decision table even if one row is already satisfied.
The engine evaluates the next row in a decision table only when all the condition stubs of a row are satisfied. However, if this property is set to false, theengine evaluates all other rows even if all the condition stubs of a row do not get satisfied.
Note
Rows are mutually exclusive should be set to true and Return multiple matches should be set to false for normal decision table evaluation.
Customer.getID() |
Customer.getName() |
Customer.setName() |
Customer.setAge() |
---|---|---|---|
1 |
John |
a |
25 |
2 |
* |
b |
30 |
* |
* |
John |
- |
Input>
Customer id=1 , name = John
Output>
Only action of row 1 will be satisfied.
Customer name=a, age=25
Output>
Only action of row 1and row 3 will be satisfied.
Customer name=John, age=25
Input Customer id=1 , name = Kumar
No action will be fired.
Action of row 3 will be fired.