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-120556 · Issue 180535
Dirty prompts functioning with JAWS
Resolved in Pega Version 7.1.8
When a dirty work object is closed, you are warned with a dirty prompt. When this dirty prompt is sourced via the modal/section pyDirtyCheckConfirm, JAWS did not gain focus to read this prompt and a manual click on this was required to read any elements. This was an issue where JAWS wasn't reading the dialog because there was no role attribute attached. This has been corrected.
SR-120564 · Issue 179056
"Configurable Error Section" option now supported by JAWS
Resolved in Pega Version 7.1.8
It was reported that a custom error section on top of the harness created using the "Configurable Error Section" option was not being read by JAWS . This was due to the custom work flow section not being supported in the out-of-the-box PRPC Accessibility Mode, and the necessary support has been added.
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-120592 · Issue 183002
Corrected circumstanced list views called from within a section
Resolved in Pega Version 7.1.8
A circumstanced List view based on a property was not being properly called from within a section. Instead of passing the primary page which has the circumstance property details for the ruleset work flow, a new page was always created. Since the new page did not have the circumstance property details, the circumstanced list view was skipped. To correct this, the Rule-Obj-ListView.DisplayView rule has been modified to always pass the primary page instead of creating a new one.
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.