Salesforce Decode
Salesforcedecode
Back to questions
OmniStudioArchitect (Hardest)omniscriptinsuranceorchestration

Design OmniScript architecture for complex insurance policy issuance

Real World Scenario

A P&C carrier needs multi-step policy application with rating, underwriting rules, document generation, and payment within Experience Cloud for agents and direct customers.

Expected Answer

• Break OmniScript into modular reusable sub-OmniScripts: applicant info, coverage selection, rating, payment • Use Integration Procedures for server-side orchestration combining multiple DataRaptor and API calls • Conditional visibility and branching based on product type and jurisdiction • Save for later/resume with omniscript saved session and authentication binding • Separate read-only review step before submission with explicit confirmation • Error handling with user-friendly messages and support reference codes from IP failures • Performance: lazy load steps and minimize synchronous callouts per step transition

Follow-Up Questions & Answers

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

Main difference: use case and scale. Break OmniScript into modular reusable sub-OmniScripts: applicant info, coverage selection, rating, payment. Use Integration Procedures for server-side orchestration combining multiple DataRaptor and API calls. Pick based on your integration pattern and team capability. OmniScript complexity belongs in Integration Procedures—keep steps focused on UX not business orchestration spaghetti. Document the decision in an ADR and align with enterprise standards.

Architect Perspective

OmniScript complexity belongs in Integration Procedures—keep steps focused on UX not business orchestration spaghetti.