You are here:
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.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with Loyalty Management or Rebate Management |
Key Terms
| Term | Description |
|---|---|
| Business Rules | Rules based on which a decision table provides outcomes. The business rules must be part of a standard object, custom object, or custom metadata type. A decision table can read up to 100,000 rules. |
| Term | Description |
|---|---|
| Source Object | Lets you select the object or the custom metadata type that contains the business rules that the decision table reads. |
| Input | Fields from the business rules that the decision table uses to evaluate records. |
| Operators | Identify how values are evaluated against the input field. Select an operator for each business rule field that’s used as a decision table input. |
| Output | When one or more rules match, these fields from the business rules contain the values that the decision table provides as outcomes. |
| Sort Order | When a decision table provides multiple outcomes, the outcomes are first sorted based on the selected input or output field. The outcomes provided by the decision table are then sorted based on the value of the selected field in the outcome’s record. Outputs can’t be sorted based on picklist and multi-select picklist type input or output fields. |
| Input Fields Condition | Selects a condition for the input fields. When the decision table input fields evaluate values and the condition matches, outcomes are provided. |
| Custom Logic | Must match for the decision table to provide outcomes. |
| Group By | Improves the performance of the decision table by grouping business rules with a widely used input field. |
| Term | Description |
|---|---|
| Dataset Link | Allows you to select fields from multiple objects whose values are evaluated by the decision table. Map object fields with the decision table input fields to show the decision table which field values to evaluate. |
| Term | Description |
|---|---|
| Decision Table action | Invokes active decision tables. You can invoke a decision table to evaluate records of a dataset link. You can also invoke a decision table without a dataset link and enter details about what the decision table evaluates. |
| Term | Description |
|---|---|
| Refresh | Ensures that the decision table reads new and updated rules. |
Workflow
- Define an object or a custom metadata type that contains the business rules.
You can add the rules either to standard objects or to custom objects or custom metadata types that you created.
- Create a decision table:
- Select the object or custom metadata type that contains the business rules.
- Select the input and output fields.
- If necessary, create one or more dataset links.
Use the dataset to determine which field values the decision table evaluates. You can select fields from up to 5 source objects.
- Invoke the decision table in a flow.
You can also invoke a decision table by using a Connect API.
- If necessary, update the business rules and refresh the decision table.
How a Decision Table Provides Outcomes
