OmniStudioIntermediateflexcardrefreshintegration-procedure
Architect FlexCard refresh strategy after Integration Procedure post-transaction updates
Real World Scenario
Agent completes payment IP; Account FlexCard still shows outstanding balance until manual browser refresh frustrating call center.
Expected Answer
• IP completion event OmniStudio pub-sub trigger FlexCard refresh
• FlexCard refresh action re-run Extract DR not full page reload
• Optimistic UI interim state Processing payment until refresh confirms
• Parent-child FlexCard coordination payment card refreshes balance card
• Debounce refresh avoid double IP on rapid actions
• Error state refresh shows failed payment not stale success
• Test refresh chain all dependent FlexCards update
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: IP completion event OmniStudio pub-sub trigger FlexCard refresh Also consider: FlexCard refresh action re-run Extract DR not full page reload In practice: Optimistic UI interim state Processing payment until refresh confirms Balance speed of delivery with maintainability.
Architect Perspective
Stale FlexCard after IP is UX bug—pub-sub refresh must be standard pattern post-transaction.