As per the link it is mentioned that the edit validate rule is a client side validation.
As per my understanding the java code is executed on the server side so how can say that the edit validate rules is client side validation
Hi @KarthikM6254: Though you write the java code for a edit validate, based on the property defined in the harness / section, the edit validates are also loaded in the client side when the HTML is loaded for the screen. Said that it doesn’t required to communicate to server for validation.
In the other case, validations which you do on form submit are not loaded with the HTML and those are done in server side.
Hope this helps.
Thanks
@KarthikM6254
If you select the option in the harness level (client side), certain OOTB edit validate has the corresponding javascript code (pega_validators.js). By this way it is working as the client side. But for the custom edit validates which was created as part of the application, it definetly works a server side validation.
As per me, edit validate is not a complete client side validation. Whatever the corresponding js functions for the edit validate in the pega_validators.js works as the client side. The other edit validates are definetly executes on server side.
@P.Siva.Praveen Yes agree on this so ideally we cannot call them as client side validation as the .class file related functions cannot be executed by browsers. This topic needs to be corrected and proper reference details to be mentioned.