Choosing Omniscript data actions and invoke modes
Which Omniscript action fits each data job (Data Mapper Extract, Turbo, Transform and Post, Delete, Integration Procedure, Docusign), when a single Data Mapper is enough and when an Integration Procedure is needed, and how Invoke Mode, Use Future and User Message properties shape what the user experiences.
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 · 8 practice questions ·
What the exam expects
- Choose the Omniscript action for a data job: read, read one object fast, reshape, write, delete, orchestrate several steps, or collect a signature.
- Apply the "When to Use" rules to decide between a single Data Mapper and an Integration Procedure.
- Recommend a prefill design whose output names match the Omniscript element names.
- Pick Invoke Mode (Default, Non-Blocking, Fire and Forget) or Use Future from whether the user must wait and whether the response matters.
- Set the user's feedback while an action runs and when it fails.
Key terms: Data Mapper action (calls a Data Mapper Extract, Turbo Extract, Transform or Load from the Omniscript); Integration Procedure action (calls a server-side procedure that can run many steps); Invoke Mode (the action's response behavior); Response JSON Path (the node of the response returned to the Omniscript); User Message properties (texts shown during and after a remote action).
Key facts
- Detail
- Restructures data; doesn't read or write Salesforce data
- Detail
- Single object; no formulas or complex field mappings; nested array output
- Detail
- Host the Post action in an Integration Procedure
- Detail
- Needs at least two Data Mappers, so use an Integration Procedure
- Detail
- Path to Id with a merge field; optional confirmation modal
- Detail
- Shown in the debug console, not applied to the data JSON
- Detail
- Future method; returns no data to the Omniscript
- Detail
- Template fields mapped from the Omniscript with a Data Mapper Transform
Sources for this section (6)
- Data Mapper Actionshelp.salesforce.com (opens in a new tab)
- When to Usehelp.salesforce.com (opens in a new tab)
- Delete Actionhelp.salesforce.com (opens in a new tab)
- Action Propertieshelp.salesforce.com (opens in a new tab)
- IP Actionhelp.salesforce.com (opens in a new tab)
- Action Elementshelp.salesforce.com (opens in a new tab)
- Why can't a Data Mapper Transform action delete a record the user removed?
- When does an Omniscript save need an Integration Procedure instead of one Post action?
- Why might Fire and Forget be chosen over Non-Blocking?
- Which property relabels the continue button when a remote action fails?
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 (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams