SR-120454 · Issue 188836
Fixed error handling for MDB listener
Resolved in Pega Version 7.1.8
JMS MDB listener was failing and throwing 'NoClassDefFound' errors in the PegaRULES log file. The issue was found to be the error reporting in one of the integration methods, and has been fixed by modifying the ServiceAPI.generateErrorMessage such that if LogHelper cannot be used, an error is reported in the system error file and the listener continues.
SR-120455 · Issue 184325
Toolbar enhanced for large decision tables
Resolved in Pega Version 7.1.8
An enhancement has been added to decision table columns to change the toolbar to floating if there are many columns to display.
SR-120468 · Issue 184320
Appearance order retained for multiple swimlanes
Resolved in Pega Version 7.1.8
After putting multiple swimlanes in a flow, the order of their appearance was returning to the original state after saving it. This was caused by the rendering being performed in the order the server store/sent the swimlane data. To ensure proper behavior, the swimlanes are now reordered based on the swimlane layout (horizontal, vertical) and their coordinates before being rendered.
SR-120468 · Issue 185827
Appearance order retained for multiple swimlanes
Resolved in Pega Version 7.1.8
After putting multiple swimlanes in a flow, the order of their appearance was returning to the original state after saving it. This was caused by the rendering being performed in the order the server store/sent the swimlane data. To ensure proper behavior, the swimlanes are now reordered based on the swimlane layout (horizontal, vertical) and their coordinates before being rendered.
SR-120477 · Issue 180530
Smoothed navigation for multiple screen trees
Resolved in Pega Version 7.1.8
In a tree navigation screen flow with multiple screens, the screens have client side validations which were not working when navigating from the tree navigation control link but did work when the "Next" or "Back" buttons were clicked. This was found to be a problem in the work flow UI doc submit method where validation was skipped if the Activity was "GoToPreviousTask". To resolve this, a check was added (previousEntryPoint) if submit is called from back button of screen flow.
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.