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.
SR-C24201 · Issue 373198
Updated logging to stabilize ServiceAPI use
Resolved in Pega Version 8.1
When using “ServiceAPI” for other integrations within the application, setting ServiceAPI to “Fatal” caused the loss of visibility on issues with other components of the application which use ServiceAPI. This was traced to excessive logging for authentication failures from ServiceAPI, and has been resolved by changing error logging to Warn or Debug at various instances.
SR-C24370 · Issue 371308
Autocomplete text alignment fixed with Microsoft Internet Explorer div check
Resolved in Pega Version 8.1
Using the Microsoft Internet Explorer browser, an autocomplete list of 50 items was shown as overridden by a vertical Scroll bar. This was caused by a div error on the gridLayoutWrapper, and has been corrected with the addition of a check for Microsoft Internet Explorer when calculating the gridLayoutWrapper div width.
SR-C24382 · Issue 372081
103
Resolved in Pega Version 8.1
In order to improve performance, internal 'When' results will now be cached.