Loading
Business Rules Engine
Considerations for Creating Decision Tables

You are here:

  1. Salesforce Help
  2. Docs
  3. Business Rules Engine

Considerations for Creating Decision Tables

Before you plan and create decision tables in your Salesforce org, review these considerations.

Required Editions

Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions for clouds that have Business Rules Engine enabled
Note
Note If you use decision tables as part of Loyalty Management or Rebate Management, see Decision Table.
  • You can use only the objects that have the CreatedDate and IsDeleted fields as source objects to create a decision table.
  • You can group a table’s rows by up to two input fields that use the Equals operator.
  • You can use a field’s sequence number only once in a custom logic.

    For example, the custom logic (1 AND 2) OR (1 AND 3) is invalid. Instead, define the logic as 1 AND (2 OR 3).

  • By default, a decision table can have 30 input fields and five output fields.

    Configure input fields so that during lookup, a maximum of 10 input fields are considered. This field aggregation can be achieved by using the AND operator in the table's input condition logic to join up to 21 required columns that use the Equals operator.

Example
Example Configure a Decision Table Logic to Bring Input Columns Down to 10

A table has seven required input fields that use the Equals operator.

Here’s how the table’s input condition logic is configured.
(1 AND 2 AND 3) OR 4 OR (5 AND 6 AND 7)

When the table is activated, fields 1, 2, and 3 are joined and considered as one field. Field 4 is considered as an independent field. Fields 5, 6, and 7 are joined and considered as one field.

During lookup, even though the active table is considered to have three input fields, you can pass input values for all seven input fields. The output is based on the values passed for the seven input fields.

 
Laster
Salesforce Help | Article