Introduction
An alternative to the whole-screen dialog used in applications with the Windows interface generated in Java and .NET, has been implemented. This alternative provides greater interaction with end users by performing validations and calculations as the data is typed.
So far, Windows interface applications generated with .NET and Java, performed field validations when clicking the Confirm button. After the introduction of the GeneXus Olimar version, the validations and calculations are performed as the fields are filled, allowing greater control over them.
Description
Client level validation at is an alternative to server validation . It enables a substantial increase in Transactions interaction with end users. This is achieved by validating the data and calculating formulas as users move through the screen fields and/or type information in them.
Client level validation does not prevent server validation from taking place. The latter is always performed in order to ensure the integrity of the data and avoid record blocking while end users are entering data.
For this reason, a Transactions rules can be executed more than once. It is necessary to keep this in mind if the rules call programs that update the database.
The processing of the data entered by end users occurs in full screen, meaning that there is no per-level saving. Particularly, if we use the insertion in a typical invoicing Transaction as an example, the heading is not saved in the database when end users are typing in the detail. In the same example, the same happens with each detail line. These are not saved after each of them is finished.
Another important aspect to consider about this dialog, taking once again the typical invoicing example, is that there is no program-based method for adding detail lines. Calling a procedure that adds lines in an invoicing Transaction detail, for instance, is not possible.
A general recommendation is that rules should not involve calls to objects with interface (other Transactions, Work Panels, etc.) or objects that update the database.
In order to enable client level validation, there is the models property inside the "User Interface" group, called "Client Side Validation".
This property enables the selection of the interaction level with end users of Transactions for Windows applications.
Values
Yes: Activates validations and calculations as end users enter data in the different screen fields. Validations and calculations are repeated when users activate the Enter event.
No: Stops validations and calculations as end users type data in the different screen fields. All the validations and calculations take place once users activate the Enter event.
Default value = No
There is also a property with the same name at the Transaction object level, inside the "Java and C# Specific" group, where apart from the above-mentioned values, it has the "Use model's property value." This value shows that the model's property value will be adopted for either enabling this behavior or not. The latter is the default value.
For more information about the GeneXus Olimar version:
http://www.genexus.com/olimar