In a screen that lists the results of an aggregate with Fetch=AtStart, which event will be triggered more than once?

In a screen that lists the results of an aggregate with the Fetch set to AtStart, each time the screen is rendered, the OnRender event is triggered. This event is associated with the presentation layer and occurs every time the screen is displayed or refreshed. Consequently, if an action on the screen causes a refresh or if the user navigates back to the screen, the OnRender event fires again, allowing for updates to the UI with the latest data or state.

This behavior is important for dynamically updating content based on user interactions or changes in data without needing to reload the entire screen. The OnRender event is significant in scenarios where the UI needs to reflect the most current state of information after an aggregate fetch.

The other events such as OnInitialize, OnLoad, and OnDestroy are executed at specific times in the lifecycle of a screen. OnInitialize occurs when the screen is first created, OnLoad happens after initialization but before rendering, and OnDestroy is triggered when the screen or its components are being destroyed. Consequently, these events are not triggered repeatedly as the screen is navigated or refreshed, making OnRender the only event that occurs multiple times during these interactions.