Show TOC

Creating a Decision TableLocate this document in the navigation structure

Procedure

  1. In the Rules Navigator view, expand the project node and select the ruleset or flow ruleset.

  2. Under the Decision Tables section, choose New... .

  3. In the Add New Decision Table dialog box that appears, enter the name of the decision table.

  4. Choose Next .

  5. Select the conditions from the Available Conditions section and choose Add .

    Note

    You can change the order of a condition by selecting it and choosing the Move Up or Move Down button as required.

  6. Choose Next .

  7. Select the actions from the Available Actions section and choose Add .

    Note

    You can change the order of an action by selecting it and choosing the Move Up or Move Down button as required.

  8. Choose Finish .

  9. In the decision table editor, expand the decision table, under the General Infomation section, you can set the following properties to true or false for a decision table:

    • Return Multiple Matches

      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.

    • Rows Are Mutually Exclusive

      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, the engine evaluates all other rows even if all the condition stubs of a row do not get satisfied.

      Rows are mutually exclusive should be set to true and Return multiple matches should be set to false for normal Decision Table evaluation.

Note

In the decision table editor, you can choose the Condition button and in the menu that appears, you can choose any of the following options:

  • Add Vertical Condition

  • Add Horizontal Condition

    You can arrange the condition and action columns of the decision table depending on how you want them to appear. If you choose to have only vertical conditions, all condition headers appear in vertical columns in the decision table. On the other hand if you choose to have a horizontal condition, one of the condition headers and the corresponding values gets arranged in a row.

  • Add Other Condition

    More Information: About Other Condition

  • Change Condition

  • Remove Condition

You can also choose the Action button and in the menu that appears, you can choose any of the following options:

  • Add Action

  • Change Action

  • Remove Action

Return multiple matches

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.

Rows are mutually exclusive

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, the engine 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.

More Information