In the screen lifecycle, where does the preparation run?

In the screen lifecycle, the preparation phase occurs on the server. This step is crucial as it is responsible for retrieving data and setting up any necessary logic before the screen is actually rendered and sent to the client's web browser. During this phase, the server generates the necessary information based on the user's context and interaction, ensuring that any required data is available when the client receives and displays the screen.

Since the preparation runs on the server, it allows for processing that requires access to server-side resources, such as databases or external APIs, ensuring that all data needed for the user interface is ready before the user's browser starts to render it. This server-side execution enhances performance and security as it abstracts direct database interactions away from the client.

Other options suggest running the preparation on the browser, client-side, or within the database, which does not align with how the OutSystems framework is designed to optimize screen delivery and user experience.