Child Omniscripts, embedded Flexcards and custom LWCs
How to embed reusable child Omniscripts, place Flexcards in an Omniscript with the Custom LWC element and the Update Omniscript action, and build custom LWCs that extend OmniscriptBaseMixin or run standalone with the omniaggregate event.
Use child Omniscripts, Flexcards, and custom LWCs for enhanced interactivity and complex UI configurations.
~8 min read · 11 practice questions ·
What the exam expects
- Build a reusable Omniscript, embed it in parents and predict what happens on activation and on clashing node names.
- Embed a Flexcard with the Custom LWC element, pass it data and write its selections back with an Update Omniscript action.
- Meet the requirements for a custom LWC and choose between extending OmniscriptBaseMixin and running it standalone.
- Use the mixin methods to update the data JSON, navigate, save state and make remote calls.
- Send data from a standalone component with the omniaggregate event, knowing what the Communicate page says about the pubsub module on Standard Runtime.
- Know what the exam expects of custom LWC code, and how the Industry Process Library supplies ready-made script elements.
Key terms: reusable Omniscript (a child script marked Reusable and dragged into parents), Custom LWC element (the element that places a custom component or Flexcard in a step), OmniscriptBaseMixin (the base a custom LWC extends to work with the data JSON), standalone LWC (a component that doesn't extend the mixin), omniaggregate (the event that builds nodes inside the Custom LWC element).
Key facts
- Detail
- A reusable Omniscript can't contain another
- Detail
- Only the first child's values are set
- Detail
- Updates every activated parent after Proceed
- Detail
- cf + card name, such as cfAccountCard
- Detail
- Result stored in a new node
- Detail
- Must be true in the XML configuration file
- Detail
- A Step or a non-repeatable, non-nested Block
- Detail
- false: object input merges
- Detail
- Not supported; clone first
- Detail
- Communicate page: doesn't operate on Standard Runtime; use wpm or ssm
Sources for this section (7)
- Embed an Omniscripthelp.salesforce.com (opens in a new tab)
- Embed Flexcardshelp.salesforce.com (opens in a new tab)
- Update from a Flexcardhelp.salesforce.com (opens in a new tab)
- LWC requirementshelp.salesforce.com (opens in a new tab)
- Custom LWC Elementhelp.salesforce.com (opens in a new tab)
- Mixinhelp.salesforce.com (opens in a new tab)
- Communicate to an LWChelp.salesforce.com (opens in a new tab)
- Why must each reusable child use unique Element Name nodes in Set Values?
- Which Property Name refreshes an embedded Flexcard whenever the passed-in Omniscript data changes?
- Why does omniApplyCallResp fail on a tracked property passed directly?
- Which Property Name passes a record Id into an embedded Flexcard?
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 (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams