OmniStudioArchitect (Hardest)integration-procedureclaimsreusability
Design reusable Integration Procedure library for insurance FNOL claims intake
Real World Scenario
Auto home and commercial lines each built separate FNOL IPs with duplicate vendor lookup and policy validation logic.
Expected Answer
• Core IP library: ValidatePolicy LookupVendor GeocodeLoss AssignAdjuster
• Line-of-business wrapper IP calls core plus line-specific steps
• Version core IP semver breaking changes coordinated all LOBs
• Catalog Confluence developer portal IP input output JSON schema
• CoE certification required before production IP publish
• Regression golden JSON tests each core IP
• Deprecate duplicate IPs migration timeline per LOB
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Core IP library: ValidatePolicy LookupVendor GeocodeLoss AssignAdjuster. Line-of-business wrapper IP calls core plus line-specific steps. Pick based on your integration pattern and team capability. FNOL IP duplication across LOBs is maintenance tax—core library with LOB wrappers standard. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
FNOL IP duplication across LOBs is maintenance tax—core library with LOB wrappers standard.