INC-138041 · Issue 590556
Handling added to ensure proper Data-Admin-DB-Table name records
Resolved in Pega Version 8.6
As part of property optimization, after exposing the property "SolutionName" using the wizard, the value was not visible in a new column for existing records after the completion of the column population job. This was traced to an issue with DBSchemaDDLExecutor expecting lowercase Data-Admin-DB-Table names, and the wizard has been updated to ensure Data-Admin-DB-Table name records are all lowercase.
INC-138243 · Issue 584898
Performance improvement in When parsing
Resolved in Pega Version 8.6
After upgrade, performance issues were seen in the execution of rules with When conditions. This has been resolved by modifying the code to address some inefficiencies in the parsing method.
INC-138253 · Issue 597570
Handling added to ensure proper Data-Admin-DB-Table name records
Resolved in Pega Version 8.6
As part of property optimization, after exposing the property "SolutionName" using the wizard, the value was not visible in a new column for existing records after the completion of the column population job. This was traced to an issue with DBSchemaDDLExecutor expecting lowercase Data-Admin-DB-Table names, and the wizard has been updated to ensure Data-Admin-DB-Table name records are all lowercase.
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.