You are here:
How Result Filters Work
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.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions for clouds that have Business Rules Engine enabled |
When you create a decision table, choose one of these filtering options based on your requirements and on how you want to use the results in the subsequent steps of a workflow or a process.
| Filter Result By | Result Type | Description |
|---|---|---|
| First Match | Single Outcome | If your input yields multiple results from the lookup, this option shows the first record in the decision table’s source object. |
| Output Order | Multiple Outcomes | If your input yields multiple results, this option shows all the matching results based on the order of the matching records in the decision table’s source object. |
| Any Value | Single Outcome | When your table has multiple rows with an identical combination of input and output values, this option returns the output values from only one of the rows. If the combination of your lookup values has only one matching output, this option returns the single matching output value. If the combination of your lookup values has multiple, different matching outputs, this option returns an empty response. |
| Serial Number | Car Type (Required Input) | City (Optional Input) | Daily Fees (Output) |
|---|---|---|---|
| 1 | Hatchback | New York | 50 |
| 2 | Hatchback | San Francisco | 48 |
| 3 | Hatchback | Chicago | 45 |
| 4 | Sedan | New York | 60 |
| 5 | Sedan | Chicago | 55 |
| 6 | Sedan | San Francisco | 58 |
| 7 | Sedan | New York | 60 |
| 8 | SUV | New York | 80 |
| 9 | SUV | Chicago | 75 |
| 10 | SUV | San Francisco | 78 |
| Results Filtered By | Flow Configuration | Lookup Values | Flow Output | Explanation |
|---|---|---|---|---|
| First Match | Include the Car Type input column for lookup | Sedan | 60 | Here, the flow looks for the value Sedan in the decision table. Rows 4, 5, 6 have the value Sedan in the Car Type input column. But the flow returns 60, which corresponds to Sedan and New York because it’s the first matching value in the table. |
| Output Order | Include the Car Type input column for lookup | SUV | 80, 75, 78 | Here, the flow looks for the value SUV in the decision table. Rows 8, 9, 10 have the value SUV in the Car Type input column. The flow returns the matching results for the three rows based on their order in the source object. |
| Any Value | Include the Car Type and City input columns for lookup | Sedan, New York | 60 | Here, the flow looks for the values Sedan and New York in the decision table. Rows 4 and 7 have the values Sedan in the Car Type and City input columns respectively. Because the input and output values for the two columns are identical, the output returns the single value 60. |

