Shaping Integration Procedure output for client components
Which Integration Procedure action shapes data for a Flexcard or Omniscript: Response Actions for trimming, early exits and status codes; Set Values for literals, calculations and strings; Data Mapper Transform actions for XML, value translation, lists and nulls; List Actions for merging; and paging for long loops.
Recommend approaches for strategically utilizing Data Mapper Transform, Set Values, and Response actions within an integration procedure to transform, filter, and structure data before sending it to the client-side component.
~8 min read · 14 practice questions ·
What the exam expects
- Recommend a Response Action to trim the reply, return only a defined structure, exit early under a condition, or set the HTTP status code.
- Recommend Set Values for literals, renamed nodes, simple calculations and string building, including TOSTRING for large identifiers.
- Recommend a Data Mapper Transform action for XML, value translation, list conversion and null handling, and Ignore Cache when one caller must skip the transform's cache.
- Configure the intent of a List Action merge (merge fields, sort, replacement values) and plan paging for long loops.
Key terms: Response Action (ends the procedure and returns data to its caller); Additional Output (key-value pairs added to the returned JSON); Set Values (sets values in the data JSON from literals, merge fields or formulas); Data Mapper Transform action (calls a Transform on the data JSON, in memory); List Action (merges lists by matching node values).
Key facts
- Detail
- Ends the procedure and returns data to the caller
- Detail
- Discards other data; disable Return Full Data JSON
- Detail
- A Response Headers key that overrides the HTTP status code
- Detail
- Multiple Response Actions with Execution Conditional Formulas
- Detail
- Scientific notation by default; wrap in TOSTRING
- Detail
- No node by default; Include null values in the response
- Detail
- Flattened and merged into one object
- Detail
- Disables the Transform's caching for that action
- Detail
- Must be lists, even with one item
- Detail
- Over 1000 items degrades performance; page the list
Sources for this section (8)
- Response Action for Integration Procedureshelp.salesforce.com (opens in a new tab)
- Integration Procedure Best Practiceshelp.salesforce.com (opens in a new tab)
- Set Values Action for Integration Procedureshelp.salesforce.com (opens in a new tab)
- Map Inputs and Outputshelp.salesforce.com (opens in a new tab)
- Transforming Lists with Data Mappershelp.salesforce.com (opens in a new tab)
- Omnistudio Data Mapper Transform Actionhelp.salesforce.com (opens in a new tab)
- List Action for Integration Procedureshelp.salesforce.com (opens in a new tab)
- Work with Data and Listshelp.salesforce.com (opens in a new tab)
- Why does an early-exit Response Action need an Execution Conditional Formula?
- When should a consultant wrap an IF function in TOSTRING?
- Why does a List Action break when its data source returned only one item?
- What makes a Transform keep empty fields as nodes?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 31 lessons of the Omnistudio Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (14 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams