Question
Tata Consultancy Services
IN
Last activity: 13 Aug 2018 5:51 EDT
Displaying "Value cannot be blank" Error message Twice in UI
Hi All,
I have a email field and it's required only in certain condtion's, for this i configured a when rule .
The required condtion is working properly but i am getting "Value cannot be blank" error message twice .(Attached the screenshots for your reference)
Let me know what is the route cause for this??
Regards,
Bharath
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
IN
Hi,
From screenshots, I reckon these are two different messages
"Value cannot be blank"
and
"Value cannot be blank:"(followed by ":" )
Better to raise an SR to find out what's happening.
Regards,
Ashish
Pegasystems Inc.
FR
Hello,
I personally never seen this issue before. It look like you have 2 validations firing and setting the same error message.
Do you see anything on the tracer?
Pegasystems Inc.
IN
Hi,
As per my understanding you have given that field as required in property rule form and also explicitly you are firing one more validation on it.
Please do verify it once.
Regards,
Vinay Reddy
-
Ravi Kumar Pisupati Sudit Sengupta Marc Cheong
Tata Consultancy Services
IN
Hi Vinay,
I am not running any explicit validation on it.
Regards,
Bharath
Pegasystems Inc.
IN
Hi,
Yeah Okay, they confirmed that its a bug in pega systems code then use the approach that they have mentioned in below comments.
Regards,
Vinay Reddy
CollabPartnerz
IN
Looks like you are firing validations twice on two properties.Could you please check once.
CollabPartnerz
IN
Can you please share the validation rule if possible.
-
DivyaKrishna V
CollabPartnerz
IN
Are you using repeating dynamic layout?
Could you please share the snapshots of your Configurations.
Vodafone
IN
Hello Bharath,
This seems like a bug in Pegasystems code. If you are using the repeating dynamic layout use the below local change to fix the issue in userworkform
Local-change:
<style>
#gridBody_right table.gridTable td .iconErrorDiv .iconError::after{
content:none
};
</style>
else identify the parent section and apply.iconError:after{content:none;}
This should fix reported issue.