Omniscript data flow: action placement and round trips
How data moves through an Omniscript journey: where read, transform and save actions sit, when an action runs as a button or between Steps, why Pre- and Post-Transforms cost a trip, how responses reach elements, how parent and child Omniscripts share action values, and when an Omniscript call belongs in a reusable, cacheable Integration Procedure.
Provide guidance on the appropriate Data Mappers and Integration Procedures to use within an Omniscript to efficiently fetch, transform, and save data to meet specific business outcomes.
~8 min read · 9 practice questions ·
What the exam expects
- Place each data action where the journey needs it: reads at the start of a Step, saves at the end or in the last Step, on-demand checks as a button inside a Step.
- Cut server round trips by bundling the actions between two Steps into one Integration Procedure.
- Explain why a Pre- or Post-Transform Data Mapper on an action costs an extra trip, and when to move the reshaping into the procedure.
- Route responses into the right elements (Response JSON Path and Node, Turbo Extract arrays, asynchronous responses) and trim what is sent.
- Decide where action values go when a parent and a child Omniscript share an Integration Procedure action.
- Justify moving an Omniscript's own HTTP call into an Integration Procedure that can be cached and reused.
Key terms: round trip (one client-to-server call); Pre-/Post-Transform Data Mapper (server-side reshaping of an action's request or response); Send/Response Transformations (trim and reparent JSON); Extra Payload (extra key-value pairs an action sends).
Key facts
- Detail
- Button inside a Step or Block; remote call between Steps
- Detail
- Use an Integration Procedure to reduce round trips
- Detail
- Runs on the server, returns the request body to the client
- Detail
- No Pre/Post Data Mapper transforms, no large attachments
- Detail
- Nested array; Response JSON Path such as Account|1
- Detail
- Set values in the parent Omniscript
- Detail
- Caching, chaining, list merging, invocation from Apex, REST, Flow
Sources for this section (6)
- Omniscript Action Elementshelp.salesforce.com (opens in a new tab)
- Omniscript Best Practiceshelp.salesforce.com (opens in a new tab)
- Common Action Element Propertieshelp.salesforce.com (opens in a new tab)
- Omniscript Data Mapper Action Elementshelp.salesforce.com (opens in a new tab)
- Retrieve Data with an Integration Procedurehelp.salesforce.com (opens in a new tab)
- Integration Procedure Features Not in Omniscriptshelp.salesforce.com (opens in a new tab)
- Why trim the request with Send JSON Path and the response with Response JSON Path on an Integration Procedure action?
- When should a Data Mapper Post action be hosted in an Integration Procedure rather than placed directly in the Omniscript?
- Why do elements with default values miss a Non-Blocking procedure's response?
- What happens to an asynchronous Integration Procedure call if the user navigates away from the Omniscript?
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 (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams