---
schema_version: "1"
id: 6a44e9ee3f51601f130726b0405e045397c205320f22a72c81bdc2ab037f1c5a
title: Process Multiple Decision Table Outputs Without a Context Definition
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/bre_process_multiple_dt_outputs_without_context.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.bre_process_multiple_dt_outputs_without_context.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 52d194ce46d4fdf1504fd86506ea8ba1564c2463605056344a9722d959fdfde9
description: Use a decision table that returns multiple outputs for a single set of input values in any expression set, even if the expression set isn't associated with a context definition. When you turn on Process Multiple Decision Table Outputs while mapping a Lookup Table step's variables, Expression Set Builder automatically creates and maps the local list variables you need to use every matching result in later calculation or logic steps.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Process Multiple Decision Table Outputs Without a Context Definition

Use a decision table that returns multiple outputs for a single set of input values in any expression set, even if the expression set isn't associated with a context definition. When you turn on Process Multiple Decision Table Outputs while mapping a Lookup Table step's variables, Expression Set Builder automatically creates and maps the local list variables you need to use every matching result in later calculation or logic steps.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions for clouds that have Business Rules Engine enabled</td></tr></tbody></table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-business_rules_engine-264-0-0-production-enus/b2d6dd5c-c231-428b-abbf-3dd2cd51a11f/images/icon_note.png)

Note Before you can process multiple outputs in a Lookup Table step, set the decision table's Filter Result By to **Output Order**. See [How Result Filters Work](https://help.salesforce.com/s/articleView?id=ind.bre_how_decision_table_result_filter.htm&release=264.0.0&type=5 "When you create a decision table, you can specify how you want the table’s results to be filtered. The filter you choose determines whether you get a single matching result or multiple. If there are multiple results, filtering also determines the order in which the results appear.").

Unlike the context-tag mapping used in context-aware expression sets, this option doesn't require a context definition. Expression Set Builder creates a local list node variable to represent the set of matching rows, and a local list attribute variable for each output column, then automatically maps them to the decision table's output columns. You can then use these local list variables in later Calculation, List Group, or List Filter steps, or with list functions such as LISTSUM, LISTSIZE, and LISTAVG.

![Example: Plan Add-ons Case Study](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-business_rules_engine-264-0-0-production-enus/b2d6dd5c-c231-428b-abbf-3dd2cd51a11f/images/icon_example.png)

Example: Plan Add-ons Case Study

Miguel, a rule designer at a telecommunications company, wants an expression set that returns every add-on available for a customer's plan type, along with each add-on's price. He creates the Plan\_Addons decision table with the input column Plan\_Type and the output columns Addon\_Name and Addon\_Price, and sets Filter Result By to **Output Order** so the table returns every matching row. Miguel's expression set isn't associated with a context definition. Here's how he configures the expression set version:

- Adds a Lookup Table step and selects the Plan\_Addons decision table.
- Clicks Map Variables, and turns on Process Multiple Decision Table Outputs.
- Expression Set Builder creates a local list node variable, Plan\_Addons\_Results, and two local list attribute variables, Addon\_Name and Addon\_Price, and maps them to the decision table's output columns automatically.
- Adds a Calculation step that uses LISTSUM on Addon\_Price to calculate the combined cost of all available add-ons.

To test the configuration, Miguel simulates the expression set version using the Advanced input mode.

```
{
  "Plan_Type": "Family Unlimited"
}
```

Because Plan\_Type matches three rows in Plan\_Addons, the simulation returns all three matching add-ons in the Plan\_Addons\_Results list, and the Calculation step returns the sum of their prices.