Interface data must update automatically every minute without user interaction. How should this be configured?

Interface data must update automatically every minute without user interaction. How should this be configured?

• A. Query the data inside a local variable used to display the departure times. Set the refresh interval to "1".
• B. Use a timer node to refresh on a schedule.
• C. Refresh automatically by the platform.
• D. Manual refresh only.

Answer: (A)

Automatically updating the interface data every minute is achieved by tying the data that powers the display to a refreshable local variable and setting its refresh interval. In this approach, the query that retrieves the departure times lives in a local variable, and you configure that variable to refresh every minute. With the interval set to 1, the query runs on a timer, so the displayed times update without any user action. This uses the interface’s built-in refresh mechanism to keep data current. Using a timer node belongs to a process model, not the interface, so it won’t apply to an interface-only refresh. There isn’t a separate platform-wide automatic refresh for interfaces, and relying on manual refresh requires user interaction, which doesn’t meet the requirement.

Automatically updating the interface data every minute is achieved by tying the data that powers the display to a refreshable local variable and setting its refresh interval. In this approach, the query that retrieves the departure times lives in a local variable, and you configure that variable to refresh every minute. With the interval set to 1, the query runs on a timer, so the displayed times update without any user action. This uses the interface’s built-in refresh mechanism to keep data current.

Using a timer node belongs to a process model, not the interface, so it won’t apply to an interface-only refresh. There isn’t a separate platform-wide automatic refresh for interfaces, and relying on manual refresh requires user interaction, which doesn’t meet the requirement.