How do you configure a FlexCard to refresh data after an action?

How do you configure a FlexCard to refresh data after an action?

• A. Only refresh on explicit user request via a separate button.
• B. Use a data binding refresh or an event-driven data source, and optionally trigger an Integration Procedure to refresh and push updated data.
• C. Disable refresh to prevent latency.
• D. Data cannot be refreshed after an action.

Answer: (B)

When a FlexCard needs to show up-to-date data after an action, the refresh happens by re-reading the card’s data source rather than relying on a static result. You can configure a data binding refresh so that, after the action, the card re-executes its bound data source to pull fresh values. Alternatively, use an event-driven data source that responds to a specific event (such as the completion of an action) to trigger a refresh automatically. If you need server-side processing before updating the UI, you can run an Integration Procedure to fetch or compute new data and then push those updated values back into the FlexCard. This combination keeps the card synchronized with backend data without requiring a separate refresh control. Disabling refresh or claiming data cannot be refreshed after an action isn’t valid, and while you could rely on a separate button, it’s not the only or best approach—the card can auto-refresh via data binding or event-driven sources, with optional Integration Procedures to ensure the latest data is shown.

When a FlexCard needs to show up-to-date data after an action, the refresh happens by re-reading the card’s data source rather than relying on a static result. You can configure a data binding refresh so that, after the action, the card re-executes its bound data source to pull fresh values. Alternatively, use an event-driven data source that responds to a specific event (such as the completion of an action) to trigger a refresh automatically. If you need server-side processing before updating the UI, you can run an Integration Procedure to fetch or compute new data and then push those updated values back into the FlexCard. This combination keeps the card synchronized with backend data without requiring a separate refresh control.

Disabling refresh or claiming data cannot be refreshed after an action isn’t valid, and while you could rely on a separate button, it’s not the only or best approach—the card can auto-refresh via data binding or event-driven sources, with optional Integration Procedures to ensure the latest data is shown.