You are here:
How Source Filters Work in Decision Tables
Narrow down the source object rows by using source filters when the source object has many rows. Use source filters to consider only relevant records from a large pool of records for decision-making.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions for clouds that have Business Rules Engine enabled |
| Supported Data Type | Operators |
|---|---|
Text Static enum Dynamic enum |
|
Number Double Percent Currency Integer Long DateOnly DateTime |
|
Boolean ID |
|
Example Consider a decision table with these columns and rows:
| INPUT | OUTPUT | ||
|---|---|---|---|
| Serial Number | Product Name | Status | Product CODE |
| 1 | P1 | Active | P101 |
| 2 | P2 | Inactive | P202 |
| 3 | P2 | Active | P200 |
| 4 | P1 | Inactive | P108 |
| 5 | P1 | Active | P105 |
| 8 | P1 | Active | P202 |
| 9 | P2 | Inactive | P101 |
| 11 | Active | P303 | |
| 12 | Inactive | P300 | |
To consider only the rows that have Product Name as P1 and Status as Active, then create the source filter this way.
- Product Name Equals P1
- Status Equals Active
The results for these source filters are rows with Serial Number 1, 5, and 8. The decision table performs the lookup during actual run time for only these records from the source objects.
Did this article solve your issue?
Let us know so we can improve!
