SR-119780 · Issue 175524
Added accessibility for CalendarViewGadget's month switch
Resolved in Pega Version 7.1.8
The CalendarViewGadget's month switch arrow buttons/icons have been updated to support navigation with the keyboard and respond to the TAB key, allowing full access to this function within the accessibility framework.
SR-119978 · Issue 184032
Corrected handling for properties in XML rule
Resolved in Pega Version 7.1.8
When using properties mapped on the root element of an XML SOAP rule, the attributes were mapped properly but the element value was not. In a related error, after giving ParseXML rule invocation values for Type Substitution for Parse XML, the XML was not mapped to the clipboard for the type substituted elements. There was a workaround of using DSS 'switchtooldassembler', but this has been fixed by updating parsexmlsaxrulewrapper.
SR-120224 · Issue 178688
Potential vulnerability closed in XML stream generation
Resolved in Pega Version 7.1.8
A potential security issue was found with the XML stream generation and runtime, and has been corrected.
SR-120329 · Issue 178133
Assembler compatibility issue resolved
Resolved in Pega Version 7.1.8
After upgrade, web services that modify the Header were failing due to a compatibility issue with the default assembler. While there was a workaround of giving the value of 'true' to the dynamic system settings 'Owning ruleset: Pega-IntegrationEngine' and 'Setting purpose: switchtooldassembler', this has been resolved.
SR-120381 · Issue 179868
TopLevelClass updated to accept a hyphen in the name
Resolved in Pega Version 7.1.8
Previously, the new application wizard Top-Level class did not support the use of a dash between two ruleset classes. An enhancement has been added to allow this format.
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-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.