OmniStudioAdvancedflexcardagent-desktopui
Design FlexCard architecture for agent desktop 360 views
Real World Scenario
Call center agents need unified view of customer policies, claims, billing status, and next best action on Service Console homepage.
Expected Answer
• FlexCard composition: header card customer summary, related list cards policies claims
• Data sources: DataRaptor Extract or Integration Procedure feeding card datasets
• Actions on card: launch OmniScript, navigate to record, click-to-dial telephony integration
• Conditional card states based on customer segment or open case priority
• Performance: limit cards per page and defer load below fold
• Responsive layout for console vs Experience Cloud agent portal
• Version FlexCards with deployment pipeline like other metadata
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. FlexCard composition: header card customer summary, related list cards policies claims. Data sources: DataRaptor Extract or Integration Procedure feeding card datasets. Pick based on your integration pattern and team capability. FlexCards excel at composable agent UX—avoid monolithic single card doing everything with 12 IP calls. Optimize for scale and operational observability.
Architect Perspective
FlexCards excel at composable agent UX—avoid monolithic single card doing everything with 12 IP calls.