When invoking an Expression Set that is associated with a Context Definition from an Integration Procedure (IP), the input payload must be formatted correctly to enable the Expression Set to retrieve the Context Record and evaluate the expressions.
Unlike standard Expression Set executions, it is not necessary to pass the entire Expression Set input payload. First build the Context and get the Context and pass only the Context Record Id. The Context Record Id must be provided using a specific node naming convention based on the Context Definition Name - <ContextDefinitionName>Id.
Resolution:
To execute an Expression Set that is linked to a Context Definition from an Integration Procedure, provide the input in the following format:
If the Built Context Definition is:
ContextId: ‘8d4966b8cb3bfb9a71e1394bc1bbc91f6ba2958411796ad24ae52b7e6fc6b22d’
Then the input to the Expression set is:
{
"inputs": [
{
"testId": “%ContextId%”
}
],
"options": {}
}
Important Considerations
005385774

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.