Child Omniscripts, embedded Flexcards, LWCs and branding
When to reuse a child Omniscript, how to embed a Flexcard and pass it Omniscript data, where the Custom LWC element can go, when to extend or override a standard element instead, how to brand with stylesheets and right-to-left styles, and how an Omniscript talks to other LWCs on the Standard Runtime.
Advise on leveraging LWC (Lightning Web Component) Embeds and Custom/Standard Components within Omniscripts, including Child Omniscripts for reuse, or Flexcards to enhance the user experience and maintain corporate branding.
~7 min read · 9 practice questions ·
What the exam expects
- Recommend reusable child Omniscripts for repeated process fragments, and plan reuse before building.
- Embed a Flexcard in an Omniscript and choose how it gets its data (its own query or the Omniscript's records).
- Choose between the Custom LWC element, overriding one element, and mapping a whole element type, and respect their placement and runtime limits.
- Analyze which UX/UI changes a branding requirement needs: stylesheet, right-to-left stylesheet or design tokens.
- Recommend how an Omniscript sends data to a separate LWC on the Standard Runtime.
Key terms: reusable Omniscript (a child embedded in parent Omniscripts); Custom LWC element (places a custom component, or a Flexcard, in a Step); LWC Component Override (replaces one element with an extended component); static resource stylesheet (CSS named in Styling Options); Messaging Framework (Pub/Sub, session storage and window post message properties).
Key facts
- Detail
- A reusable Omniscript can't contain another reusable Omniscript
- Detail
- Adopts the parent script's configuration; element names must be unique
- Detail
- cf prefix, Flexcard needs Omniscript support
- Detail
- parent-data true plus records maps Omniscript data to the card
- Detail
- Omniscript support off plus Standalone Mode
- Detail
- A Step or a non-repeatable, non-nested Block
- Detail
- "useCustomLMS": true in the Setup JSON
- Detail
- Not supported in Safari
- Detail
- Doesn't operate; use window post message or session storage
Sources for this section (7)
- Embed an Omniscripthelp.salesforce.com (opens in a new tab)
- Embed Flexcardshelp.salesforce.com (opens in a new tab)
- Pass Data to an Embedded Flexcardhelp.salesforce.com (opens in a new tab)
- Custom LWC Elementhelp.salesforce.com (opens in a new tab)
- Override an Elementhelp.salesforce.com (opens in a new tab)
- Custom Styleshelp.salesforce.com (opens in a new tab)
- Communicate to an LWChelp.salesforce.com (opens in a new tab)
- Why outline every Omniscript before building any of them?
- When should an embedded Flexcard use Standalone Mode?
- Why can't SLDS design tokens alone carry the branding for every user?
- Which Setup JSON property lets an element override communicate with the Standard Runtime components?
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