Question
Wipro Limited
US
Last activity: 3 Oct 2016 10:48 EDT
Error message on top of local action (model dialog)
Hi All,
I have a navigation rule- when user selects one action in it, it will display a section with Email ID text box with a submit button. On click of Submit with out entering any value or in-valid email ID, the system allowed to submitting.
We need to display a message on top of the modal dailog to enter valid email ID.
Any suggestions are welcome.
Thanks,
Naresh K.
***Updated by moderator: Marissa to update categories***
Blue Rose Technologies GmbH
DE
Can you configure a validate rule in flow action rule form(the local action which is configured to open in the modal dialog) and make it to fail as and when the flow action is submitted ? After this exercise, let me know where the error message is getting displayed.
Blue Rose Technologies GmbH
DE
Did you see the errors getting set to the clipboard page ?
If that is the case, then you can selectively show the Errors section (with Applies to @baseclass) in modal dialog using hasMessages when rule.
Pegasystems Inc.
IN
Hi
Which version you are on ? Per this Support Article " https://pdn.pega.com/support-articles/local-flow-action-validation-fails-modal-popup " this issue is a known bug and was scheduled to be resolved in 7.1.7
Pegasystems Inc.
IN
Hi,
Could you please check the applicability of the below articles for your use-case.
https://community.pega.com/support/support-articles/flow-modal-dialog-not-showing-error-messages
https://community.pega.com/support/support-articles/issue-validation-modal-flow-action
Areteans Technologies
AU
1. How did you validated the email property. Is it through flowaction(localaction) validation rule or through post activity or an edit validate rule?
2. Make the field mandatory check in validate rule/property level.
3. Check the template which local action uses, you can override the template and make the neccessary changes.
Wipro Limited
US
Hi Dharanitharan,
I tried all the approaches that you explained above but the problem persists. So i thought this needs to be customized the code to achieve this logic and as above said this is known bug and addressed in 7.1.7