Which type of variables can a screen have in OutSystems?

In OutSystems, screens can have various types of variables to manage data effectively during the screen's lifecycle. Local variables are used to store temporary data that is specific to the screen and is not intended to be used outside of that screen context. Input variables, on the other hand, allow data to be passed into a screen from other parts of the application, enabling users to interact with the screen by providing relevant information.

When a screen includes both input variables and local variables, it allows for a more flexible design. Input variables enable the screen to receive external data, essential for dynamic applications that need to reflect user input or information from other entities. Local variables can process this input data or store intermediate results relevant to the user’s interactions on that screen.

Therefore, the correct answer includes both input and local variables, as it embodies the essential capabilities of screens to handle data. Screens can leverage these variable types to maintain a robust interaction model, effectively managing both the data provided to them and the data they generate during user interactions.