You are here:
Create a Decision Table That Uses a Standard Evaluation Object
If you use Product Qualification, Product Disqualification, Product Category Qualification, or Product Category Disqualification objects to store the evaluation criteria, use predefined templates to easily create decision tables.
Required Editions
| View supported products and editions. |
| User Permissions Needed | |
|---|---|
| To create a decision table: | Manage Product Catalog AND Rules Engine Designer |
| To use a decision table: | Rules Engine Runtime |
- From the Product Catalog Management app’s home page, click Qualification Rules.
-
From the Qualification Decision Tables page, click
New.
The Basic Details page appears.
-
On the Basic Details page:
-
Enter a name, API name, and description.
Tip Add the purpose of the decision table to the decision table name to specify whether the decision table is meant for qualification or disqualification. For example, if you’re creating a qualification decision table for furniture, name the decision table FurnitureQualify. -
Select an application usage type.
To create a decision table for product qualification or disqualification, select Product Qualification. To create a decision table for product category qualification or disqualification, select Product Category Qualification.
- Select a template.
- Click Save & Next.
-
Enter a name, API name, and description.
- On the Preview & Save page, click Finish.
-
Click Edit.
The Basic Details page appears.
-
Based on the number of records in your decision table, select a decision table
type.
If the number of records in the decision table is less than 100,000, select Standard. If the number of records in the decision table exceeds 100,000, select Advanced.
- Retain the application usage type.
-
Click Save & Next.
The Condition & Results page appears.
-
Retain the default source object.
Note Skip the Related Objects field because rules are defined on only the source object. -
To narrow down rows from the source object, add filters.
- Click Source Filter.
- To add a filter, click Add Filter, and then select a source object field, operator, and a value.
- If you add more than one filter, use the Filter Logic field to specify the logic by using AND or OR.
-
In the Conditions section, add the fields that you want to use as input. To add
a field:
- Click Add Condition.
- In the Source Object Field, select the field name.
-
Select an operator.
The operator determines how a particular field from the business rule evaluates a record or a user-specified value.
- If necessary, set the condition as optional.
To know about the permissible number of input and output fields, see Considerations for Creating Decision Tables. -
Select a condition type.
When you use custom logic, the Number column indicates the sequence number of the fields. For example, you have three input fields and you want to use custom logic that provides output when fields 1 and 2 match or when field 3 matches, specify the condition as: (1 AND 2) OR 3.
-
In the Results section, ensure that the IsQualified field or the IsDisqualified
field is available.
For a decision table used for product or category qualification, ensure that IsQualified is available. For a decision table used for product or category disqualification, ensure that IsDisqualified is available.
-
In the Results section, add other fields that you want in the decision table
output. To add a field:
- Click Add Results.
- In the Source Object Field, select the field name.
-
Click Save & Next.
The Behaviours page appears.
- In the Filter Result By field, select First Match.
- If necessary, select an input or output field by which records must be sorted and then select the sort order.
-
To consider columns with null values during lookup, select Consider
Null Values for Lookup.
See How Null Values Work in Decision Tables.
Note The Consider Null Values for Lookup option is available only when the decision table type is standard. -
Click Save & Next.
The Preview & Save page appears.
- On the Preview & Save page, review the information, including the conditions and preview records, and then click Finish.
Note If you used custom fields in decision tables, use change sets or package manager to first
deploy the custom fields to your destination org before you deploy the decision
tables.
Did this article solve your issue?
Let us know so we can improve!

