Salesforce Decode
Salesforcedecode
Back to questions
OmniStudioAdvancedlwccustom-widgets

Design Omniscript Custom Lightning Web Components

Real World Scenario

Standard OmniScript inputs cannot render interactive coverage map selector.

Expected Answer

• Custom LWC registered as OmniScript element • Pub-sub between custom LWC and OmniScript JSON model • Validate custom element accessibility • Test LWC isolated and embedded in OmniScript • Upgrade compatibility Salesforce releases • Minimize custom LWC count maintainability

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Direct answer: Custom LWC registered as OmniScript element Also consider: Pub-sub between custom LWC and OmniScript JSON model In practice: Validate custom element accessibility Optimize for scale and operational observability.

Architect Perspective

Custom LWC extends OmniScript—each widget is maintenance liability budget carefully.