Which event is specifically available for Screen Aggregates and data actions?

The choice "After Fetch" is specifically available for Screen Aggregates and data actions because it corresponds to the lifecycle of data retrieval in OutSystems. When you work with Screen Aggregates, the "After Fetch" event gets triggered immediately after the data is successfully retrieved from the source, allowing you to perform any necessary operations or logic on that data before it is presented to the user. This is particularly useful for scenarios where you want to manipulate or validate the data after it has been fetched but before it is displayed on the screen.

This event provides a dedicated point in the life cycle of data handling where developers can insert processes like data formatting, validation, or additional calculations. The timing of this event ensures that such operations can be performed with the most up-to-date information before it reaches the UI.

In contrast, other events listed, like "Ready," "Render," and "Destroy," have different roles in the application lifecycle. For instance, "Ready" pertains to the screen lifecycle before any data is fetched, while "Render" happens as the screen is being displayed, and "Destroy" relates to cleaning up resources when the screen is no longer active. Thus, "After Fetch" is uniquely suited to handling operations immediately following data retrieval, which aligns perfectly