SR-120518 · Issue 180099
Corrected error handing on"Post Action on Click Away"
Resolved in Pega Version 7.1.8
When an assignment in a screen flow was configured to use the "Post Action on Click Away" setting, it was not possible to go back if there were validation messages on the screen. Without the "Post Action on Click Away" setting, the click back worked and the validation message was cleared by the jumpToTask activity. This work flow issue has been fixed by clearing the page error messages before calling performflowaction.
SR-120525 · Issue 186509
Added handling for special characters in PDF Eforms
Resolved in Pega Version 7.1.8
PRPC uses a third-party library 'iText' to read and write PDF 'Eform' documents. It was found in some cases that if the input document contains fields ("Acrofields") that contain special characters (in particular the '#' hash/pound symbol) and/or accented characters, then the iText library would throw an error. To eliminate this, a check of the Field Name has been added to ensure it has a value before doing anything with it. If it is empty, that will be logged. As a workaround, it was found that by editing the input PDF file (using an appropriate third-party editor/generator) and ensuring that no field names ("Acrofields") contained special characters or accented characters, the iText library (and then subsequently the PRPC activity "GenerateEform") was able to process the input file and correctly produce the 'filled-in' output PDF 'EForm'.
SR-120566 · Issue 181231
Bulk Actions filtering error resolved
Resolved in Pega Version 7.1.8
In Bulk Actions, if a filter was renamed from "Assigned to Operator" to something else, ex "Application ID", the filter was not being applied. If the "Assigned to Operator" filter was deleted and a new one added, the filter was applied correctly. This was found to be an issue with the filters "Assigned to Operator" and "Assigned to Workbasket" setting the flag pyUsage = operator on the filter condition, causing a custom SQL to be generated. This has been corrected.
SR-120585 · Issue 182421
Work object history corrected for failed flow action submissions
Resolved in Pega Version 7.1.8
If a a flow action is submitted which encounters errors and generates Page-Messages, correcting the errors and re-submitting the flow action created duplicate entries in the work object history that included entries for the failed flowaction submission. This was caused by improper rollback of the addhistory when the commit of the WO is rolled back, and has been corrected.
SR-120586 · Issue 179198
Assignment dependencies with child cases now properly resolve
Resolved in Pega Version 7.1.8
Using a dependency on an assignment based on a child case can case an error. This was due to the obj class being wrongly populated, and has been resolved.
SR-120586 · Issue 178686
Assignment dependencies with child cases now properly resolve
Resolved in Pega Version 7.1.8
Using a dependency on an assignment based on a child case can case an error. This was due to the obj class being wrongly populated, and has been resolved.
SR-120596 · Issue 183801
Resolved mapping issue for SOAP-connect with multirefs
Resolved in Pega Version 7.1.8
After upgrade, mapping the soap-connect response to page in activity was not working as expected. This was an issue with a Parse-XML rule, and has been corrected with added support for multirefs and SOAP arrays with multirefs.
SR-120701 · Issue 179702
Email listener error handling improved
Resolved in Pega Version 7.1.8
When an email arrived with a zero byte attachment, the email listener was failing to generate a work object. An error was seen in the log, and the listener marked the email as seen even though no WO was created. This has been fixed by suppressing the IOException that arises while processing a zero-size INLINE attachment, allowing the rest of the email message to be processed. An exception will be logged, but the attachment that caused the issue will not be added to the work object.
SR-120730 · Issue 178759
Fixed FCM access for remote work item attachments
Resolved in Pega Version 7.1.8
When using FCM to access remote work item via find by ID, attempting to open the history / attachments popup generated a green tick (success but no content) on the first attempt and the error "Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'HISTORYANDATTACHMENTS' that applies to '@baseclass'" on subsequent attempts. "the operation completed successfully, but returned no content". The issue only happened when first logging on and searching for a work item and did not occur if the tab was closed and the same work item reopened. This was caused by the prgateway sending an HTTP request where the Pega thread name in the URL was stripped of a slash, triggering the creation of a brand new Pega thread where expected pages were missing. To resolve this, the code has been updated to correctly maintain slashes and add them if necessary.
SR-120899 · Issue 183642
Work object history corrected for failed flow action submissions
Resolved in Pega Version 7.1.8
If a a flow action is submitted which encounters errors and generates Page-Messages, correcting the errors and re-submitting the flow action created duplicate entries in the work object history that included entries for the failed flowaction submission. This was caused by improper rollback of the addhistory when the commit of the WO is rolled back, and has been corrected.