Create a Decision Table

You create decision tables to use for dynamic offer prioritization, policies, price components, and filters.

Before you begin

Create the objects that use decision tables.

About this task

This procedure explains how to create a decision table from the My MATRIXX Pricing and Configuration interface. You can also create a decision table from within the pricing item that contain it (by clicking Create Decision Table in the pricing item table pane).

Procedure

  1. In Decision Tables, click New Decision Table.
  2. In Create New Decision Tables:
    1. In Name, enter a unique name.
    2. (Optional) In Description, enter descriptive information about its purpose.
    3. (Optional) In External ID, enter any alphanumeric character to serve as a unique ID on this pricing object. The external ID can be used for any reason that is meaningful to your implementation of MATRIXX Engine. External IDs are saved to the pricing configuration file and loaded into the Pricing database.
    4. Click Create.
  3. (If needed) In Edit Decision Table, change the general properties (the name, description, or external ID of the item) and click Save.
    Note: Any time you edit the value of a general property, you must click Save for your changes to take effect. The values you enter for other fields in Edit Decision Table are automatically saved.
    • If the decision is to be based on a single-parameter condition, follow the instructions below in the Single-Parameter Decisions section.
    • If the decision is to be based on multiple-parameter conditions, follow the instructions below in the Multiple-Parameter Decisions section.
Single-Parameter Decisions

If the decision is to be based on a single-parameter condition, do the following:

  1. Click Add Row.

    Leave the single row that was added (that has no value) unpopulated (do not add data to it).

    The decision table is successfully created. You can now assign the decision table to the pricing item tables that are intended to use this decision table for single-parameter based decisions.

  2. (Optional) Assign the decision table to the component table of the pricing item that will use it and populate the single row with a normalizer value.

    For example, from within a rate table, assign this decision table by clicking Select Decision Table in the rate table workspace, and then specify the single rating formula by clicking the edit icon in the result cell and entering the appropriate values in the formula dialog box.

Multi-Parameter Decisions

If the decision is to be based on multiple-parameter conditions, do the following:

  1. For each normalizer to add to the decision table, perform the following steps.
    1. Click Add Column.
    2. Select the normalizer from the list.
    3. Click Add.
  2. For each possible combination of the normalization parameter values you want the decision table to normalize on, perform the following steps.
    1. Click Add Row.
    2. Click the cell in each normalizer column and select a parameter value from the list.

    If needed, you can clone or delete any row that has been added:

    • To clone one or multiple rows, click in the checkbox of each row you want to clone (to clone all rows, click the checkbox in the table header), and then click Copy Rows. The clones are added to the decision table.
    • To delete one or multiple rows, click in the checkbox of each row you want to delete (to delete all rows, click the checkbox in the table header), and then click Delete Rows.

    The decision table is successfully created with the multiple-parameter condition set you defined.

  3. (Optional) Assign the decision table to the component table of the pricing item that will use it and assign a result value for each condition-set row of the decision table.

    For example, from within a policy table, assign this decision table by clicking Select Decision Table in the policy table workspace, and then in the results column of the policy table, specify the policy profiles that apply to each condition-set row of the decision table.

What to do next

You can reuse the decision table in any component table that you want.