INC-138265 · Issue 591903
Improvements made for releasing stream objects
Resolved in Pega Version 8.6
Unreleased stream resources were causing a potential memory leak that could impact performance. This has been resolved by updating the system to explicitly close store, folder and all stream objects when appropriate.
INC-138649 · Issue 585357
Timezone retrieval performance enhancement
Resolved in Pega Version 8.6
In order to improve performance and reduce a potential bottleneck for concurrent threads, PRDateTimeUtilsImpl has been updated to use a common GMT time zone object rather than getting the time zone for each operation for each function call.
INC-138743 · Issue 602445
Updated LegacyPageAdapter with forward links
Resolved in Pega Version 8.6
After upgrade, attempting to submit an assignment from an existing case type did not work, and the message "There was an error processing the 'ValidateTechnicalData' step [(no task)]: java.lang.ClassCastException: com.pega.platform.clipboard.adapters.internal.LegacyPageAdapter cannot be cast to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl" appeared on screen. Investigation showed that a reference forward link was unexpectedly referring to a LegacyPageAdapter. This has been resolved by implementing get/setNamedPageReferenceForwardLinks in LegacyPageAdapter so LegacyPageAdapter can be cast to a ClipboardPageAPI.
INC-138840 · Issue 599259
Data-Summary reports default will not use the rule resolved setting
Resolved in Pega Version 8.6
An intermittent issue was seen where a query could become stuck for ~2 hours in the database. This has been resolved by setting the default for Data-Summary reports to not use the rule resolved setting.
INC-139106 · Issue 593272
HTML Tags stripped from text email body
Resolved in Pega Version 8.6
The Service Email message data section was showing HTML tags in the email message body for both 'prefer-HTML' and 'prefer-inline' where the body was missing. Investigation showed there was no default feature for segregating the markup tags and providing the plain text when ‘HTML’ format was selected in Outlook. This has been resolved by adding a Prefer: outlook.body-content-type="text" header to get the message without HTML tags.
INC-139297 · Issue 601419
JSON content type update
Resolved in Pega Version 8.6
An update has been made to ensure the content_type is set to application/json for JSON response.
INC-139611 · Issue 587600
Timezone.getDefault function replaced for performance improvement
Resolved in Pega Version 8.6
Blocking threads were seen around the GregorianCalendarFactory.clearObject(Object) function, leading to an adverse impact on the performance.TimeZone.getDefault() is a synchronized method call, and under high load this method caused contention when more date-related APIs were invoked. To resolve this, Timezone.getDefault() has been removed and the function has been assigned to a static variable used in the clearObject() API.
INC-139619 · Issue 597333
Agent tracing handling updated
Resolved in Pega Version 8.6
When attempting to trace agents the error "Unable to trace the agent" appeared on screen. Investigation showed that the data page used by the Tracer was not always available in a thread that was displaying the section, most commonly if the section was using deferred loading. This has been resolved by using a data page available in a thread that opens a Tracer's section.
INC-139626 · Issue 592389
Enhancement added to fix corrupted operators
Resolved in Pega Version 8.6
After upgrade, an issues were seen with older operator IDs: it was not able to save the operator ID, switching the portal to admin studio was not working correctly, and it was not possible to launch the case manager portal with the migrated operator IDs. The issues were not seen with operators created after the upgrade. This was traced to corruption in the BLOB, and has been resolved by adding an enhancement to run a utility that will fix the existing corrupted operators.
INC-139627 · Issue 604761
Legacy and new ID generation logging enhanced
Resolved in Pega Version 8.6
Legacy and new ID generation logging enhancedA DuplicateKeyException was generated when attempting to create a case. The root issue was related to the local modification of the reserved ID field in the database through a custom activity and was able to to be fixed with a local change. In order to improve diagnosing events such as this in the future, enhanced logging has been added to to the legacy and new ID generation.