Input Field Conditions in Decision Tables

You are here:

Input Field Conditions in Decision Tables

When you create a decision table, select a source object for the decision table. Next, select the fields that you want to use as input and output. Finally, specify the condition logic for the input fields so that the decision table can evaluate input values or records from the object against the logic that you specify.

Required Editions

Available in: Lightning Experience

Available in: Enterprise, Unlimited, and Developer Editions for clouds that have Business Rules Engine enabled

Note If you use decision tables as part of Loyalty Management or Rebate Management, see Decision Table.

To determine when a decision table provides outcomes, select one of these input field conditions.

Condition How it Works Business Rules (Example) Evaluated Values (Example) Output (Example)

All conditions are met (AND)

The decision table evaluates the business rules against the values provided. If the evaluated values match the corresponding input fields, the decision table provides the output field values of the matched business rules as the outcomes.

Condition	How it Works	Business Rules (Example)	Evaluated Values (Example)	Output (Example)
All conditions are met (AND)	The decision table evaluates the business rules against the values provided. If the evaluated values match the corresponding input fields, the decision table provides the output field values of the matched business rules as the outcomes.	Three business rules contain three input fields and one output field. Rule 1: Input 1: Order Quantity < 50 Input 2: Product Name = Running Shoes Input 3: Product Category = Shoes Output: Discount = 5% Rule 2: Input 1: Order Quantity >=50 Input 2: Product Name = Running Shoes Input 3: Product Category = Shoes Output: Discount = 10% Rule 3: Input 1: Order Quantity >=40 Input 2: Product Name = Athletic Shorts Input 3: Product Category = Accessories Output: Discount = 7%	The decision table provides outcomes for each of the three rules. Order 1: Order Quantity: 60 Product Name: Running Shoes Product Category: Shoes Order 2: Order Quantity: 70 Product Name: Football Shoes Product Category: Shoes Order 3: Order Quantity: 20 Product Name: Athletic Shorts Product Category: Accessories	Order 1: 10% Order 2: No output Order 3: No output
Any condition is met (OR)	The decision table evaluates the business rules against the values provided. If any one of the evaluated values matches the corresponding input field, the decision table provides the output field values of the matched business rules as the outcomes.	Order 1: 5%, 10%, 7% Order 2: 5%, 10%, 7% Order 3: 5%, 7%
Custom logic	The decision table evaluates the business rules against the values provided. Based on the custom logic, if the values match, the decision table provides the output field values of the matched business rules as the outcomes. 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, you can define the logic as `1 AND (2 OR 3)`.	Logic: (1 AND 2) OR 3 Order 1: 10%, Order 2: No output Order 3: 7%

Three business rules contain three input fields and one output field.

Rule 1:

Input 1: Order Quantity < 50
Input 2: Product Name = Running Shoes
Input 3: Product Category = Shoes
Output: Discount = 5%

Rule 2:

Input 1: Order Quantity >=50
Input 2: Product Name = Running Shoes
Input 3: Product Category = Shoes
Output: Discount = 10%

Rule 3:

Input 1: Order Quantity >=40
Input 2: Product Name = Athletic Shorts
Input 3: Product Category = Accessories
Output: Discount = 7%

The decision table provides outcomes for each of the three rules.

Order 1:

Order Quantity: 60
Product Name: Running Shoes
Product Category: Shoes

Order 2:

Order Quantity: 70
Product Name: Football Shoes
Product Category: Shoes

Order 3:

Order Quantity: 20
Product Name: Athletic Shorts
Product Category: Accessories

Order 1: 10%
Order 2: No output
Order 3: No output

Any condition is met (OR)

The decision table evaluates the business rules against the values provided. If any one of the evaluated values matches the corresponding input field, the decision table provides the output field values of the matched business rules as the outcomes.

Order 1: 5%, 10%, 7%
Order 2: 5%, 10%, 7%
Order 3: 5%, 7%

Custom logic

The decision table evaluates the business rules against the values provided. Based on the custom logic, if the values match, the decision table provides the output field values of the matched business rules as the outcomes.

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, you can define the logic as 1 AND (2 OR 3).

Logic: (1 AND 2) OR 3

Order 1: 10%,
Order 2: No output
Order 3: 7%

Note For custom logic, you must specify values for all input fields in the logic.

Did this article solve your issue?

Let us know so we can improve!

Input Field Conditions in Decision Tables

Required Editions

General Information

Required Cookies

Functional Cookies

Advertising Cookies

General Information

Required Cookies

Functional Cookies

Advertising Cookies

Cookie List

Product Area

Feature Impact

Edition

Experience

Input Field Conditions in Decision Tables

Required Editions