OmniStudioAdvancedflexcardperformanceagent-console
Design FlexCard state management for multi-tab agent console performance
Real World Scenario
Insurance call center FlexCards on Account PersonAccount and Policy tabs each fire separate Integration Procedures; agents report 12-second tab switch lag during peak enrollment.
Expected Answer
• Central session cache FlexCard dataset shared across tabs via OmniStudio pub-sub
• Lazy load tab FlexCards defer IP until tab first activated
• Single IP returns Account Policy Claims bundle JSON split client-side
• Disable auto-refresh polling on hidden tabs
• Limit 3 FlexCards visible per console page not 8
• Performance budget 2 seconds tab switch measured p95
• Load test 500 concurrent agents enrollment week
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Central session cache FlexCard dataset shared across tabs via OmniStudio pub-sub. Lazy load tab FlexCards defer IP until tab first activated. Pick based on your integration pattern and team capability. Multi-tab FlexCard duplication is common perf killer—one IP bundle beats three tab IPs. Optimize for scale and operational observability.
Architect Perspective
Multi-tab FlexCard duplication is common perf killer—one IP bundle beats three tab IPs.