Support Article
Validate rule not initiated in Call for each option
SA-55026
Summary
In Pega 7.1.9, the following issues occur:
Issue 1: Validate rule invoked by the 'Call for each' option to validate a property in pxResults (Pega-Code-List) is not initiated.
Issue 2: Validation rule does not set error messages on the primary page. It instead sets them on a different Clipboard page. The error must display when the category is not selected for any file.
Error Messages
Not Applicable
Steps to Reproduce
- Add a validation rule to the pyAttachContent flow action by performing a Save As of the out-of-the-box flow action.
- In this validation rule, for each row of dragDropFileUpload.pxResults(), call another validate rule to check if the category is empty.
Root Cause
An issue in the custom application code or rules.
Issue 1. The Pages & Classes of the primary validate rule referred in the flow action does not take effect. Hence, Pega searches for the inner validate rule which checks the category of files in Work- instead of the Embed-DragDropFile. The pyClassName of dragDropFileUpload.pxResults in the validate rule XML is Work- which must be Embed-DragDropFile.
Issue 2. Despite correcting the class change, the issue persists because the error messages are set on dragDropFileUpload.pxResults. As a result, the modal dialog section whose primary page is pyWorkPage, is submitted without displaying the errors.
Resolution
Perform the following local-change:
Issue 1: Resave the validate rule which checks the category by clearing the Pages & Classes and defining them again. This corrects the pyClassName property of the pxResults and initiates the correct validate rule.
Issue 2: Set the error message on the primary page when there are errors on pxResults. Perform this in the post-processing activity of the flow action.
Published September 18, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.