Omnistudio Fundamentals18% of the exam
Omnistudio components and industry use cases
How Flexcards, Omniscripts, Integration Procedures and Data Mappers chain together in one customer interaction, how activation turns them into Lightning web components, and which tool pattern each industry (communications, energy, health and insurance, public sector) relies on, including OmniOut, OmniAnalytics and the Foundation package path.
Describe the Omnistudio solution as it applies to common customer use case scenarios in different industries (telco, energy, healthcare, public sector, etc.).
~8 min read · 8 practice questions ·
What the exam expects
- Trace how a Flexcard, an Omniscript, an Integration Procedure and the four Data Mapper types chain to read, show and save data.
- Explain what activation generates and how a standard runtime org places components on Lightning, Experience Cloud and LWR pages.
- Match industry scenarios (communications, energy, health and insurance, public sector) to an Omnistudio pattern, including Business Rules Engine calls from an Integration Procedure.
- Recognise OmniOut, OmniAnalytics tracking triggers and the Foundation package migration path.
Key terms:
- Flexcard: card-format UI that shows context and launches actions.
- Omniscript: guided, multi-step process UI.
- Integration Procedure: declarative server-side process that runs many actions in one server call.
- Data Mapper: declarative read (Extract, Turbo Extract), write (Load) or reshape (Transform) of data.
- Standard Runtime: Omnistudio on standard objects; the Managed Package Runtime uses the package's custom objects.
Key facts
Activation output
- Detail
- Activating a Flexcard or Omniscript generates its Lightning web component automatically
Standard runtime placement
- Detail
- Standard Omniscript and Flexcard components in Lightning App and Experience Builders
LWR sites
- Detail
- Omniscripts and Flexcards supported in LWR Experience sites in both runtimes
Turbo Extract scope
- Detail
- One Salesforce object type plus related-object fields; no formulas
Transform
- Detail
- Works in memory; doesn't read from or write to Salesforce objects
Rules engine
- Detail
- Integration Procedures call Expression Sets and Decision Matrices
CME check
- Detail
- Verify each component's standard runtime certification status before disabling Managed Package Runtime
OmniOut on standard runtime
- Detail
- Install a managed package in the org
Foundation package orgs
- Detail
- Standard data model on managed package runtime; migration required
Sources for this section (6)
- Omnistudio Digital Suitetrailhead.salesforce.com (opens in a new tab)
- Omnistudio Differenceshelp.salesforce.com (opens in a new tab)
- Supported Featureshelp.salesforce.com (opens in a new tab)
- Omnistudio Data Mappershelp.salesforce.com (opens in a new tab)
- Disable Managed Package Runtimehelp.salesforce.com (opens in a new tab)
- Migration blogdeveloper.salesforce.com (opens in a new tab)
- Why do developers open only the Flexcard and Omniscript designers and never a code editor for the component that runs on the page?
- When should an Integration Procedure, rather than a Data Mapper, back a Flexcard?
- Why do OmniOut components not appear in a Migration Assistant plan?
- Where do OmniAnalytics tracking triggers live on the standard runtime?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 46 lessons of the Omnistudio Developer 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