INC-137775 · Issue 583784
Improved resolved rules cache
Resolved in Pega Version 8.5.2
When Rule resolution iterated over a candidate list to fetch a candidate, performance issues were seen on very large sites. To resolve this, an enhancement has been added that will cache the resolved virtual table entries to optimize performance in high demand use cases like DSM.
INC-137882 · Issue 599139
Hazelcast will be used to determine node presence
Resolved in Pega Version 8.5.2
When calling logoff from the end user portal, sporadic PresenceStandardLifeCycleListener exceptions were seen during high load periods. This was traced to changes made in the Service Discovery behavior: when there is an issue with the node and heartbeats are missed, the node goes to Safe Mode. This caused the topology to change and trigger clearing off presence sessions, but the node still received service requests and this issue was seen. To resolve this, an updated has been made so the system will rely on the Hazelcast listener instead of service discovery to determine whether a node has left.
INC-138243 · Issue 584897
Performance improvement in When parsing
Resolved in Pega Version 8.5.2
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 597572
Handling added to ensure proper Data-Admin-DB-Table name records
Resolved in Pega Version 8.5.2
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-138743 · Issue 602444
Updated LegacyPageAdapter with forward links
Resolved in Pega Version 8.5.2
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 599978
Data-Summary reports default will not use the rule resolved setting
Resolved in Pega Version 8.5.2
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 593271
HTML Tags stripped from text email body
Resolved in Pega Version 8.5.2
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 601420
JSON content type update
Resolved in Pega Version 8.5.2
An update has been made to ensure the content_type is set to application/json for JSON response.
INC-139619 · Issue 597334
Agent tracing handling updated
Resolved in Pega Version 8.5.2
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 592392
Enhancement added to fix corrupted operators
Resolved in Pega Version 8.5.2
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.