Question
aaseya it services pvt.ltd
SA
Last activity: 13 Mar 2020 7:58 EDT
How to customize the error message of validation
How to customize the error message of default edit validate rule "NotFutureDate"?
***Edited by Moderator Marissa to update platform capability tags****
Coforge DPA
GB
Hi
The default Edit validate rule uses below field value for error message:
*/
pyMessageLabel • Enter a valid past date
Do a save as of this rule, to you application specific ruleset and update the message. It should work
Regards
Bhavya
Hi
The default Edit validate rule uses below field value for error message:
*/
pyMessageLabel • Enter a valid past date
Do a save as of this rule, to you application specific ruleset and update the message. It should work
Regards
Bhavya
Pegasystems Inc.
US
Does below pdn link help?
https://collaborate.pega.com/question/how-customize-validate-rule-error-messages
aaseya it services pvt.ltd
SA
Can Anyone help me the message rule which is called when we use "pyisPastDate" edit validate ?
I want to customize the following message
Invalid value specified for DOB. Value doesn't adhere to the Validate: pyIsPastDate
Pegasystems Inc.
JP
You need to customize edit validate rule to display message like this.
You need to customize edit validate rule to display message like this.
If edit validate supports client side validation You need to customize html fragment CustomValidators like this. Client side javascript must be in webwb pega_validators js.
Hope this information helps you.
Accenture
IN
Hello Muroa,
Thanks for the brief reply, however i am facing one issue in this. Say i have entered a wrong value and the error message popped up on screen as expected. however if the choose wrong value again the same message appears 2 times . looks like the previous message is not erased. FYI , actually my edit validate rule was not executed earlier, from google I applied this solution- on the section where i used this date property, I used post action and refresh this section action on change. after that the validation was executed. but i guess due to that my previous error message is also appearing on screen along with the second error message. Any thoughts on this please.