You can also use local list variables to store the definition’s context tag values in
the expression set version. In an expression set, local list variables are hierarchical
resources (you can create parent and child hierarchies with them), while variables and constants
are flat resources.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer
Editions for clouds that have Business Rules Engine enabled
Local list variables store variable or constant values from context definition tags. You can
create local nodes and attributes to an existing hierarchy or create a custom local hierarchy
based on your specific use case in the expression set. Use the following guidelines while
creating and using local list variables:
For a local list node variable, the parent node can be a context definition node or
another local list node variable.
For a local list attribute variable, the parent node must be a local list node variable.
You must create a local list node variable before you create a local list attribute
variable.
Once a local list variable is saved, it cannot be edited. You can only delete a local
list variable.
Local list variable names must be unique.
Local list variables must be used in the Right-Hand Side (RHS) of an expression step
before they can be used on the Left-Hand Side (LHS).
Local list variables cannot accept input from JSON, cannot be hydrated directly in a
context instance, and cannot return values to the output JSON even if marked "Include in
Output".
Local list variables inherit decimal precision settings from the left panel settings of
the expression set; they do not support individual decimal scales.
Local list variables are supported only in steps where context tags are allowed, such as
Calculation steps. They are not supported in Condition steps.
You can use a local list variable only within the expression set version, and they can’t
be accessed by subexpression sets or any external processes. The values stored by a local
list variable are not passed back to the context instance. You can't use local list
variables as an output of the expression set.
During simulation, values passed for local list variables are ignored; only default or
null values from resource initialization are used.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
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
Always Active
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
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
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.