Posted: 2 Nov 2017 19:02 EDT Last activity: 23 Jan 2018 3:39 EST
"Please correct flagged fields before submitting the form!" pop up in PRPC V7.2.1
Hi guys. We have an issue with this OOB pop-up message that appears on the accordion screen with multiple section. User only sees the pop-up error message. User require some error icon on the section where the client-side errors have occurred. While a pop up is displayed indicating that the form is missing data, no visual marker is present to easily identify the section in which error occurs. I found that there is a fix for tabbed screen, is there a fix for accordion or any other solutions?
Hi Rincy. Thank you for your reply. However we have a screen with about 5-6 section layout group with accordion display type and when this message (reported) pops up, it is time consuming and not user friendly for users to go over each collapsed section to find what was missing. I've never seen such "General" message as you are referring to. Does it mean that we need to open SR?
Hi Rincy. Looks like the first post is working (I actually implemented both to the UserWorkForm), however all error messages are now on the Clipboard and not shown to the user. The Validation rule runs from the Post Flow Action activity and runs on the context page (specified in pages and Classes). How to fix it?
Hi Erica. Just want to explain what is going on. We have the same accordion section in parent case (pyWorkPage) and child case (diff page) and the validation is on the complex internal accordion section based on the Page List property Basin(). I included Validate rule into the both post action activities of parent and child cases and for the parent case I'm still getting the error pop-up "Please correct flagged field.." and for the child case I see all the errors on the Clipboard and not on the harness. Need your advise.
I understand that on referring the local change from the post, you are able see the error popup on the Parent case. However, for child case, the errors are still appearing in the Clipboard and not on the UI.
Is my understanding correct? If yes, could you share the screenshots of the configuration made for this usecase involving Parent and child case. Also, share the screenshot of the clipboard.
As it takes too much time to find the correct approach, we considered to go with the Modal window to display all tabs. This way the user won't be able to close it until all required properties will have a value. It would fit the purpose if another issue won't pop up. Now when the child's window gets closed, the screen with the main case info gets frozen and none of the buttons is responding. Can you provide any solution to it?
Hi Rincy. Thank you for reply. I'm attaching one screenshot with Modal config, and the behavior is the same and intermittent in IE and Chrome, sometimes the buttons of the main screen, after closing Modal, become disabled.