OmniStudioArchitect (Hardest)reusabilitylibrarygovernance
Design reusable OmniStudio component library for enterprise
Real World Scenario
Five LOBs each built custom address capture and payment OmniScript steps with inconsistent validation.
Expected Answer
• Standard sub-OmniScripts: AddressCapture, PaymentCapture, ConsentCapture versioned centrally
• Shared Integration Procedures: ValidateAddress, ProcessPayment with certified interfaces
• Naming convention and catalog in Confluence or developer portal
• CoE approval for new shared components; LOB extends not forks
• Semantic versioning breaking changes communicated to all consumers
• Regression test shared components on any change
• Deprecate duplicates with migration timeline
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Standard sub-OmniScripts: AddressCapture, PaymentCapture, ConsentCapture versioned centrally Also consider: Shared Integration Procedures: ValidateAddress, ProcessPayment with certified interfaces In practice: Naming convention and catalog in Confluence or developer portal Document the decision in an ADR and align with enterprise standards.
Architect Perspective
OmniStudio reuse requires CoE enforcement—voluntary sub-OmniScript sharing fails like Apex copy-paste.