Best Practices for Advanced Decision Tables

Best Practices for Optimal Performance

• When you create an advanced decision table, if you have mandatory conditions that use the Equals operator, and the condition type is set to Custom, make sure that these conditions are grouped together in the Effective Logic field. Group these conditions to minimize the lookup complexity and improve the rule evaluation efficiency.

  For example, consider this advanced decision table where five conditions are created and the condition type is set to Custom.

  condition	source object field	operator	cOLUMN NAME	Optional?
  1	BillingCity	Equals	BillingCity	No
  2	BillingState	Equals	BillingState	No
  3	Industry	Equals	Industry	No
  4	Type	Equals	Type	No
  5	OwnerId	Equals	OwnerId	No

  For this scenario, the correct effective logic is (1 AND 2 AND 3) AND (4 OR 5).

• For smaller data changes to the object or the custom metadata associated with a decision table, use the Decision Table Refresh Action invocable action instead of doing a refresh from the decision table details page. See Refresh a Decision Table.

Best Practice for Optimal Scale

• To design a decision table with a large number of columns, group the columns by using the AND operator in the effective logic when you create the decision table.
• Use source filters when you create a decision table to pre-filter the dataset before the decision table is created. Source filters reduce the number of records that must be evaluated in the decision logic.