Question
wipro
IN
Last activity: 29 Jun 2017 15:42 EDT
Edit Validate , Edit Input-why are they called run on client side when both rely on java code--do they use applets internally??
Since Edit Validate and Edit Input both use java code,how can it be called as client side validations? is it because / does both of them internally use java applets? which run on runs in a web browser Java plugin? or something else?
Please suggest!
Pegasystems Inc.
IN
Hi Govardhan,
By default edit validate is not the client side,to get this fired on client side the corresponding javascript code for the java in the edit validate has to be defined in the pega_validators.js.The edit validates defined in the pega_validators.js are fired client side and the rest are fired on server side.
If you want the custom edit validate rule to be fired on client side then please do the following steps as per the following article:
Hi Govardhan,
By default edit validate is not the client side,to get this fired on client side the corresponding javascript code for the java in the edit validate has to be defined in the pega_validators.js.The edit validates defined in the pega_validators.js are fired client side and the rest are fired on server side.
If you want the custom edit validate rule to be fired on client side then please do the following steps as per the following article:
- Create and test the edit validate rule.
- Associate an edit validate rule with a property.
- Create and test a JavaScript function that performs the same validation test as the edit validate rule, and has the same name. Follow the structure used in the standard text file rule webwb.pega_validators.js
- Save the JavaScript in a text file rule in your application RuleSet.
- Associate with the property a control rule that includes the ClientValidation control rule.
- Enable client-side validation, by a check box on the HTML tab of the Harness form. For best results use JSP tags and the SmartFrames format for the harness.
- Reference the text file rule containing the JavaScript function on the Scripts and Styles tab of each harness that can present the field as an input field, that is, in read-write mode.
- Test.
https://community.pega.com/sites/default/files/help_v721/procomhelpmain.htm
wipro
IN
Thank you Sarab,
for sharing the details it helps , but as per step 3 above brings a issue
"3. Create and test a JavaScript function that performs the same validation test as the edit validate rule, and has the same name. Follow the structure used in the standard text file rule webwb.pega_validators.js" -
Firstly - This means we have to re-write(no code reuse but duplicating same functionality programatically ) all the configurations that we do in edit validate rule - then what is the benefit of writing/ defining edit validate rule , we can directly write validation in webwb.pega_validators.js" without defining edit validate rule.
Secondly - Pega sells the idea with clients that "Configure" only , but as per above steps we have to customize /code this which is again - against pega best practices and since clients are very focused on best practices - its a kind of conflicting situation for consultants.
&&- what about edit input ? please let me know if "Edit input" also need to have any such tweaks to make it as a client side corrections/conversion before hitting server side?