Error Message Showing at Page level, when Use Validate is entered on the advanced tab of property rule
We have a property of type date and using the OOTB validate rule NotFutureDate. If a future date is entered the message is showing on the field level, as well as the form level. Is this the expected behavior or only the field level message should be shown, though the pyWorkPage has no message?
Also we tried to give a blank custom error section, but it showed the OOTB error section.
We need to show only field level message, what is the way to hide the form level message?
We are using version 7.4
Pegasystems Inc.
US
When you add "NotFutureDate" Validate rule on your date property, you will receive the field level message if you enter a future date. This is an expected behavior.
Can you post a screen shot of your two message?
On my Pega 7.4 system, I created a use case adding "NotFutureDate" Validate rule on "pyDateTime" property. I received field level "Invalid value specified for pyDateTime" error message.
When you add "NotFutureDate" Validate rule on your date property, you will receive the field level message if you enter a future date. This is an expected behavior.
Can you post a screen shot of your two message?
On my Pega 7.4 system, I created a use case adding "NotFutureDate" Validate rule on "pyDateTime" property. I received field level "Invalid value specified for pyDateTime" error message.
What is your form level message? Is it from the Harness level?
Pegasystems Inc.
IN
Can you do a LIVE UI and check the section in the harness. Is your harness customized?
Pegasystems Inc.
IN
Hi Sam,
Have you reviewed the configuration in the "Display Options" tab in harness rule regarding the display of the errors?
Help document:
Thanks!
Celgene
US
Error 1 image shows the actual/expected field level message, while error 2 image shows the top level message.
@rachit we have a customized perform harness
@gudam I tried changing the form level errors on display harness, but nothing seemed to help.
Pegasystems Inc.
IN
Can you please let us what is customized in the harness. Also, can you check the use case with OOTB harness?
Celgene
US
Tried with the OOTB perform harness and it is behaving the same.
Also the only change in our custom perform harness is we only have the the elements of pycaseactionarea section and nothing else.