Omniscripts20% of the exam

Launching Omniscripts from pages, sites, URLs and email

How to place an activated Omniscript with the standard Omniscript component on Lightning pages and Aura or LWR Experience Cloud sites, load it from a custom LWC with the standard runtime wrapper, launch it by URL or from the utility bar, and email a link to it with DefaultOmniScriptSendEmail.

Official exam objective
Embed Omniscripts across UI components and different channels.

~7 min read · 8 practice questions ·

What the exam expects

  • Add the standard Omniscript component to a Lightning page and configure its theme, display, language and visibility.
  • Place an Omniscript on Aura and LWR Experience Cloud sites and plan for LWR-specific steps.
  • Load an Omniscript inside a custom LWC with the standard runtime wrapper.
  • Launch an Omniscript from a URL, the console and the utility bar.
  • Email an Omniscript link to a Contact, Lead or User through an Integration Procedure.

Key terms: standard Omniscript component (the Lightning App Builder and Experience Builder component that renders an activated Omniscript), LWR site (an Experience Cloud site on Lightning Web Runtime), standard runtime wrapper (the component a custom LWC uses to load an Omniscript by type, subtype and language), omniscriptEmbeddedSource (a prefill key for utility bar, flyout and modal containers), DefaultOmniScriptSendEmail (the Remote Action class that emails an Omniscript link).

Key facts

Before activation
Detail
Embedded components must be active
Display setting
Detail
On the page, or a button with an SLDS variant
LWR enablement
Detail
Contact Salesforce Customer Support first
LWR component location
Detail
Customer Interactions; Aura uses Process Automation
LWR after a change
Detail
Republish the site, including for child Omniscripts
Wrapper attributes
Detail
type, subtype, language mandatory; theme defaults to Lightning
Console tab from a URL
Detail
omniscript__tabLabel and omniscript__tabIcon
Utility bar scrolling
Detail
omniscriptEmbeddedSource = utilitybar
Email Remote Action
Detail
DefaultOmniScriptSendEmail, emailOmniScriptLink
Email template type
Detail
Custom (without Letterhead)
Sources for this section (6)
  • Why might Flexcards on an LWR site show only partial data when you open the site from Digital Experiences?
  • When does the console tab title and icon Setup property have no effect?
  • Which Omniscript does a newly dropped Omniscript component show?
  • Why can an emailed Omniscript open with recipient data already filled in?

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

Practice for the Omnistudio Developer exam