At what point does the request to an Aggregate with Fetch=AtStart get triggered?

The request to an Aggregate with Fetch set to AtStart is triggered immediately after the onInitialize event. This is important because the onInitialize event occurs when a screen is being prepared for rendering, and it’s the right moment to start fetching data that will be utilized in the screen.

When Fetch=AtStart is used, the system sends a request for the data as soon as the screen is initialized, allowing the data to be retrieved and ready for display or manipulation by the time the screen is loaded. This is crucial for ensuring that the data is available for any logic or components that depend on it during the screen's lifecycle.

By contrasting this with the other options, it can be noted that waiting until after the screen is loaded would delay data availability, and fetching data during screen rendering would lead to inefficiencies, as users would experience a lag in the data being displayed. Thus, triggering the Aggregate request right after the onInitialize event not only optimizes the performance but also enhances the user experience by ensuring that data is ready when the screen is being shown.