You are here:
Considerations for Calling Expression Sets
Before you call expression sets from Flows, Omnistudio, or third-party workflows, review these considerations.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
Before you call expression sets from Flows, Omnistudio, or third-party workflows, review these considerations.
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions for clouds that have Business Rules Engine enabled |
| Expression Set Component | Considerations When the Expression Set is Called |
|---|---|
| Input Variables |
|
| Field Aliases | If the expression set uses a field alias as a variable, pass the Id field of the source object, to which the field alias belongs, as an input to the calling workflow. |
| Decision Matrix | The active decision matrix version with the highest rank is considered. |
| Sub expression | The active sub expression with the highest rank is considered. |

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.