Decision Table

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 tables can read business rules with multiple inputs and provide multiple outputs.

Example A company provides discounts on products based on product category and price. For the product category shoes, there are two discount rules. The first rule provides a discount of 5% if the price of the shoe is $500 or lower. For shoes above $500, the discount is 10%. The third rule provides the discount for any product that's priced above $1,000. The decision table uses the product and price as inputs and the discount percentage as the outcome.

• Decision Table Key Terms and Workflow
  Let’s take a quick look at the key terms and the workflow, and at how decision tables provide outcomes.
• User Permissions for Decision Tables
  Users in your Salesforce org require specific permissions to create or invoke a decision table.
• Business Rules
  Decision tables provide outcomes based on business rules. Rules are defined as records in a standard object, custom object, or a custom metadata type. A decision table can read up to 100,000 rules.
• Create a Decision Table
  Create a decision table and select the object or the custom metadata type that contains the business rules. Select the input fields from the business rules object or the custom metadata type for the decision table to read. Select one or more output fields that contain the values that are used to calculate outcomes.
• Add Dataset Links to a Decision Table
  A decision table determines outcomes based on field values from different source objects. In a dataset link, you can map the decision table’s input fields with fields of different standard or custom objects.
• Activate a Decision Table
  Only active decision tables can be run in a flow.
• Refresh a Decision Table
  To meet evolving business requirements, you add, update, or remove business rules that the decision table reads. If you update the object or the custom metadata type that contain the rules, refresh the decision table to ensure that the outcomes are based on the latest rules.
• Invoke a Decision Table
  After a decision table is activated, invoke the decision table in a flow to provide outcomes. You can invoke a decision table based either on a schedule or on your company's requirements.
• Distribute Decision Tables
  You can share a decision table with other Salesforce orgs using change sets, managed packages, and unmanaged packages. Independent software vendors (ISV) and partners can distribute a decision table to their customers.
• Decision Tables for Developers
  Developers in your Salesforce org can employ Decision Tables developer resources to use and extend decision tables.
• Determine the Discount for Orders (Example)
  This example shows how an admin can set up a decision table to automate order discount decision process.
• 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.