How would you refresh a FlexCard after a child OmniScript, opened in a flyout, changes the underlying record?

Doing nothing leaves stale data on screen, and reloading the page is a blunt instrument that destroys the user's context.

1. Use the publish/subscribe event model. The OmniScript publishes an event when it completes; the FlexCard subscribes to that event and re-runs its data source.
2. Make sure the card's data source is not serving from a cache with a long duration, or the re-fetch will return the same stale values. Cards that participate in this pattern should either not cache or cache briefly.
3. Where the flyout is a child FlexCard rather than an OmniScript, the same mechanism applies — the child publishes, the parent listens.
4. Keep event names specific and documented. A generic 'refresh' event that every card on the page listens to means one save triggers six data source calls.
5. The fallback, a full page navigation, is acceptable only when the save legitimately ends the user's task on that page.