What type of variables can be created inside a Screen in OutSystems?

In OutSystems, a Screen can have multiple types of variables that serve different purposes for managing data within that specific context. When a Screen is created, local variables can be established to store data that is relevant only within that Screen's lifecycle. These serve to hold temporary data, user input, or computational results tied to the Screen’s functionality.

Additionally, input parameters can be defined to allow data to be passed into the Screen from other parts of the application. These parameters enable the Screen to receive necessary information when it is navigated to, facilitating dynamic content and interactions based on user actions or selections.

While output parameters are also a feature in OutSystems, they are typically associated with actions rather than directly being part of the Screen's variable definitions. This helps to clarify that while output parameters are useful in the context of actions (allowing data to be sent back after the action completes), they are not relevant as a type of variable that can be created directly on a Screen. Thus, the creation of input parameters along with local variables captures the dual role of data management in a Screen effectively.