Omnistudio Fundamentals16% of the exam
Purpose of each core Omnistudio tool
What Flexcards, Omniscripts, Integration Procedures and Data Mappers are each for, their benefits and limits, who can call a Data Mapper or an Integration Procedure, and how Flexcards and Omniscripts combine in one solution.
Explain the purpose of Flexcards, Omniscript, Integration procedures, and Data Mapper.
~7 min read · 10 practice questions ·
What the exam expects
- State the purpose of each core tool in one line, and reject descriptions that swap their roles.
- Recommend the right tool for a requirement, with the benefit and the limit that decide it.
- Explain what an Integration Procedure offers that an Omniscript lacks, and what actions and blocks are for.
- Name who can invoke a Data Mapper and an Integration Procedure.
- Describe how Flexcards and Omniscripts combine (a Flexcard launches an Omniscript; a Flexcard embedded in an Omniscript).
- Key terms: Flexcard (displays data and launches actions); Omniscript (holds the user-interaction logic); Integration Procedure (bundles server-side data integration operations); Data Mapper (transfers and transforms data); action and block (an Integration Procedure's task unit and its grouping unit).
Key facts
Omniscripts
- Detail
- Contain the user-interaction logic
Flexcards
- Detail
- Display data and launch actions
Integration Procedures
- Detail
- Bundle server-side data integration operations; many actions in one server call
Data Mappers
- Detail
- Transfer and transform data; faster to build than Apex
IP actions vs blocks
- Detail
- Actions do tasks; blocks group actions to run conditionally, cache, loop or catch errors
IP-only features
- Detail
- Caching, unit testing, chainable settings, list merging, Apex/REST/Flow invocation
Data Mapper callers
- Detail
- Integration Procedures, Omniscripts, Flexcards, Apex classes, batch jobs, REST APIs
PDF or Docusign mapping
- Detail
- Data Mapper Transform
Embedded Flexcard
- Detail
- Receives data from the Omniscript and performs its actions
Batch Action on Standard Runtime
- Detail
- Not supported (calls Vlocity Scheduled Jobs)
Sources for this section (6)
- Omnistudiohelp.salesforce.com (opens in a new tab)
- Omnistudio Integration Procedureshelp.salesforce.com (opens in a new tab)
- Omnistudio Data Mappershelp.salesforce.com (opens in a new tab)
- Integration Procedure Features Not in Omniscriptshelp.salesforce.com (opens in a new tab)
- Discover the Omnistudio Digital Suitetrailhead.salesforce.com (opens in a new tab)
- Supported Featureshelp.salesforce.com (opens in a new tab)
- Why does a design pair an Omniscript with an Integration Procedure instead of using one tool?
- When is a Data Mapper Transform the right tool?
- What are Integration Procedure blocks for?
- When would a consultant combine Integration Procedures with Flexcards?
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 (10 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams