Which variable types are NOT available in a Screen?

In OutSystems, a Screen typically utilizes various types of variables to facilitate interaction and data handling within the user interface. Local variables, input parameters, and output parameters each play unique roles in a Screen context.

Local variables are defined within the Screen and are used to store intermediate data or state information that is relevant only to that specific screen. They help manage data flow during user interactions.

Input parameters are utilized to pass information from other elements, such as the previous screens or entities, into the Screen. This allows the Screen to retrieve and display data based on user navigation and actions.

Output parameters, on the other hand, are employed to send data back to the calling element or previous screen when the user finishes interacting with the current Screen. They serve as a method to communicate outcomes or capture user choices.

However, while all these variable types have their specific purposes, it is crucial to recognize the context of their usage. Output parameters, as a variable type, are actually designed for use in actions or logic flows, rather than being directly utilized at the Screen level in the same manner as the others. Therefore, when identifying which type of variable is not applicable within the context of a Screen, output parameters stand out as the correct answer since they cannot be created