You are here:
Decision Table Capabilities and Limitations
Before you plan and create decision tables in Salesforce, make sure that you’re aware of the capabilities and limitations of decision tables.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with Loyalty Management or Rebate Management |
Note Decision tables are also available as part of Business Rules
Engine. If your org has Business Rules Engine enabled, see Decision Tables for Business Rules Engine.
Decision Table Capabilities
- A decision table can process up to 100,000 business rules.
- A decision table can contain up to 30 input fields and 5 output fields.
- A decision table can contain up to 5 dataset links.
- A decision table’s input fields can be mapped to fields of 5 source objects in a dataset link.
- An org can contain up to 10 decision tables.
- A decision table invoked by the Decision Table custom invocable action can provide up to 50 outcomes.
- Decision tables that evaluate fewer than 10,000 business rules can be cumulatively invoked up to 500,000 times per hour.
- Decision tables that evaluate more than 10,000 business rules can be cumulatively invoked up to 50,000 times per hour. This limit includes the decision tables that are invoked by using Connect REST APIs and the custom Decision Table invocable action.
- Decision tables whose business rules are grouped with an input field and evaluate fewer than 10,000 business rules can be cumulatively invoked up to 1.5 million times per hour. And decision tables that evaluate more than 10,000 business rules can be cumulatively invoked up to 150,000 times per hour. This capability is applicable for the input field that groups the data with less than 1,000 records in one group.
Decision Table Limitations
- Only objects that have the CreatedDate and IsDeleted fields can be used as source objects to create a decision table.
- A decision table can contain only one input field to group the business rules. An output field can’t be used to group business rules.
- A decision table with a group-by field can be run only if you include the input field used for grouping the business rules, while invoking the decision table.
- Always use the Equals operator when selecting an operator for the input field that’s used to group business rules.
- Always use the AND condition type when selecting the condition to evaluate.
- In the dataset link, always include the source object for the input field that's used for grouping.
Löste denna artikel ditt problem?
Berätta för oss vad vi kan förbättra!
