Question
Pegasystems Inc.
IN
Last activity: 4 Oct 2018 13:54 EDT
In layout group is there a way to Show the actual errors instead of showing "error" on top of all tabs
Here, error is shown on press of submit but end user doesn't know in which tab error is present
End user must scroll through each tab to know where error is present
Solution:
Either instead of showing "error" on top of all tabs, the actual errors(say, value cannot be blank) or an exclamation is to be thrown on the tab having error
Message was edited by: Lochan to add Category
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Pegasystems Inc.
IN
Hello Aditya Boggarapu,
There is already a feedback item FDBK-15411 created for this behavior.
Best Regards,
Mounika
Pegasystems Inc.
IN
Hello Aditya,
For what version of PRPC are you observing ?
I have tried replicating in our local 7.2 system and I could observe the same i.e it displays "Error" for any type of validation error.
I am looking into the behavior and will update here with my progress.
Best Regards,
Mounika
Pegasystems Inc.
IN
Hello Aditya,
Upon analysis, could observe that the code has been written is such a way that if there are any errors, an error table is created (if it does'nt exist already) and then sets the message. The message here is hardcoded to "Error".
Best Regards,
Mounika
Pegasystems Inc.
US
Hi ADitya
Are you using client side validations on a tabbed group layout ?
1. If yes, can you check if a post-action activity instead of client side validations help ?
2. Not sure whether this applies to your scenario : https://community.pega.com/support-articles/no-icon-tab-indicate-error-0
The steps to reproduce talks about a tabbed screen flow, which in my opinion is a typo and should have been a tabbed group layout. I'll verify.
Pegasystems Inc.
IN
Yeah, we are using layout group: tab ; There are two validations in our case.
in tab 1, Entering yes/ no radio butons field is made as mandatory
in tab 2, In activity, which runs on a local save button of that particular tab, property set messages in done in a step in activity, which sets error messages on property, when it is empty
Pegasystems Inc.
US
Hi Aditya
Locally I have noticed that when using Page-Set-Messages on post action activity does mark the tab on which the issue is.
how are you calling the activity with Property-Set-Message ?
Can you try post action activity + Page set message and check if the issue is addressed ?
Pegasystems Inc.
IN
Pegasystems Inc.
US
Accepted Solution
Pegasystems Inc.
IN
Hello Aditya Boggarapu,
There is already a feedback item FDBK-15411 created for this behavior.
Best Regards,
Mounika
-
Aditya B
Capgemini America INC.
US
HI Mounika Thatikonda, has this FDBK-15411 been implemented yet?
Pegasystems Inc.
US
The mentioned feedback item(FDBK-15411) seems to be implemented in 7.2.2.
-
Aditya B