SR-C23461 · Issue 365026
Exported Excel now displays text between angle brackets
Resolved in Pega Version 8.1
Using the Export to Excel feature on a Report Definition was stripping XML and HTML-like values from the data such as text between matching angle brackets. This was traced to recently modifications in Export to Excel: because the export generates an XLSX document and not an HTML document, HTML-like code is stripped from formatted values. However, that was being performed after unescaping special HTML characters and codes in the raw or localized value, and this caused HTML-like code in the data to be removed as well. To correct this, the system will strip HTML prior to unescaping special characters. In addition, columns which did not have valid controls assigned to them or their associated properties were borrowing logic from columns formatted by non-auto controls. This has been addressed by refactoring ReportUIFieldFactory to generate basic ReportUIField instances for unformatted columns, excluding numeric and date columns.
SR-C23556 · Issue 364797
JAWS reads table sort order
Resolved in Pega Version 8.1
To improve accessibility, the sort order of a table will be read by JAWS.
SR-C23560 · Issue 378135
Accessible 'select' button added to date/dropdown with post value
Resolved in Pega Version 8.1
An enhancement has been added to the pzpega_ui_template_dropdown.js file in the PegaWAI ruleset to allow any date / dropdown with a post value to be provided with a "Select" button when accessibility is enabled.
SR-C23650 · Issue 365164
Requestor ID masked for internal users for security
Resolved in Pega Version 8.1
In order to ensure internal users with access to logs, SMA, or operations data can not utilize a Requestor ID to hijack a session, the requestor ID will now be masked and only show a portion of it.
SR-C23701 · Issue 369858
File Listener variable modified to resolve authorization exceptions
Resolved in Pega Version 8.1
A custom JMS MDB Listener was randomly failing with the exception: "ListenerThreadPool : 3] [ STANDARD] [ ] [ ] ( internal.services.ServiceAPI) ERROR - Authorization failed, please contact system administrator. com.pega.pegarules.pub.clipboard.InvalidParameterException: InvalidParameter Class not defined in dictionary: Rule-Service-null aClassName .createPage" This error was traced to a situation where the variable mEvaluateAuthorizationCheck was getting modified by more than one listener at the same time, and has been resolved by changing mEvaluateAuthorizationCheck from a static variable to an instance variable.
SR-C23885 · Issue 369192
Further improvements to browser interaction wrap memory leak
Resolved in Pega Version 8.1
Several optimizations have been done to further address browser memory leak issues observed with each interaction wrap.
SR-C2400 · Issue 352685
RAClientCleanup will be explicitly called for JBoss app tier
Resolved in Pega Version 8.1
In a JBoss app tier environment, RAClientCleanup was not happening after scheduling the Daemons in PresenceSessionStateTrackerDaemon and PushSubscriptionCleanerDaemon, leading to exceptions that ultimately caused system issues. RAClientContainer.cleanup(); will now be explicitly called.
SR-C24026 · Issue 370794
Values correctly generated for elements with attributes in ParseXML134
Resolved in Pega Version 8.1
The new SOAP integration wizard was not creating "Value" properties in WSDL with several ComplexType elements using SimpleContent definition, though it did create properties for all the attributes. This resulted in data mapping anomalies. This was traced to a missed use case in rule generation, and the rule generation implementation has been updated to generate the "Value" property for ComplexType element with SimpleContent and configure it in the mapping rules.
SR-C24067 · Issue 369978
Apache library updated
Resolved in Pega Version 8.1
To improve security, the following updates have been made: - Apache Commons FileUpload updated to version 1.3.3 - Apache-mime4j-core has been updated to version 0.8.1 - Apache POI has been upgraded to version 3.17
SR-C24117 · Issue 364430
Added 'rules only' mode for loading UDFs
Resolved in Pega Version 8.1
The DDL generated by a migrate script can be filtered to only include rules schema changes, but the UDF loaders were not modified to handle 'rules only' mode. In order to this scenario, a rules-only option has been added for loading UDFs that can be used during Apply Rules Schema Objects.