When are validations only performed in OutSystems?

In OutSystems, validations are primarily designed to occur when data is submitted to the server. This means that the data entered by the user is not immediately validated as they type or interact with the UI; instead, validation is deferred until the user initiates a submission action, such as clicking a button to save or submit the form.

This server-side validation approach helps ensure that all the data being processed and stored adheres to the defined rules and constraints. It also simplifies the validation logic since the server has access to the complete context of the data being submitted, which allows for more comprehensive checks. By validating only on submission, it also minimizes the amount of immediate feedback required on user input, reducing distractions and streamlining the user experience.

The other choices imply a more continuous or immediate validation process that doesn't align with how validations are structured in OutSystems. Validations performed when data is entered or when a widget is clicked would typically pertain to real-time validation scenarios which are not the default behavior in the OutSystems environment. Similarly, stating that validations are always performed on client-side does not capture the essential characteristic of when and how validations occur in this platform.