INC-163791 · Issue 633297
JobScheduler time zone display expanded
Resolved in Pega Version 8.5.4
The Time zone control on the JobScheduler rule form displayed only the first few characters for the time zone. This was due to a hard-coded CSS setting for the width, and has been resolved.
INC-163863 · Issue 632426
Monthly agents run correctly on non-English locales
Resolved in Pega Version 8.5.4
Nodes with non-English locales were not starting when using an Agent with a monthly execution pattern. This was due to incorrect handling of the user locale, and has been resolved.
INC-163985 · Issue 635146
Class mapped to CustomerData is incrementally indexed as expected
Resolved in Pega Version 8.5.4
When using a class which mapped to customerdata, instances that were added/updated were not automatically getting indexed unless a full reindex was performed. If the class mapping was changed from customerdata to pegadata then the incremental indexing was done. To resolve this, the UpdateProcessor class that resolves CustomerData to the correct database name has been updated to use PegaData. ConfigurationMapImpl contains the resolution mapping and a call is made to ConfigurationMapImpl to retrieve the correct database name.
INC-164021 · Issue 638639
Java object type removed from pyStream to resolve GetFile class error
Resolved in Pega Version 8.5.4
It was not possible to perform Property-Set on pyStream(java.io.InputStream) to assign it with another object of type(returned by pxGetFile RUF). This was caused by a strongly typed java.io.stream in the pyStream property creating conflict at runtime with S3WrapperInputStream from the D_GetNewFile call, and has been fixed by removing the java object type from pyStream.
INC-164308 · Issue 634410
UseNoCacheHeaders default expiration set to "0"
Resolved in Pega Version 8.5.4
When the prconfig/HTTP/UseNoCacheHeaders/default was set true it used the value "Expires: Thu, 01 Dec 1994 16:00:00 GMT". This has been updated to the more commonly used setting "0".
INC-164405 · Issue 640185
Enhancement added to support incremental update
Resolved in Pega Version 8.5.4
In order to support incremental updates between versions of Pega and versions of Oracle, an enhancement has been added that will allow the engine to handle a mix of database version and JDBC driver version and issue the query that will work on Oracle 11g database despite using a newer driver version.
INC-164472 · Issue 635114
Performance improvements for archiving and purging
Resolved in Pega Version 8.5.4
Archiving and purging jobs were not working in Prod. Investigation showed this was caused by the system timing out. To resolve this, improvements have been made to purging by batching the deletions and refactoring the Where condition to simplify the complex expression queries that determine the cases to be archived.
INC-165335 · Issue 638773
ClipboardContext updated to handle nested page lists
Resolved in Pega Version 8.5.4
The Append and Map to method was looping over the top-level pages instead of specific page in the JSON transform. This resulted in a null when trying to get the children of the page list property because the updateClipboardContext() for updating the mapping used only the immediate parent. To resolve this, the updateClipboardContext() function has been modified to include the context for the root element so finding the children of the page list property works as expected in a nested page structure.
INC-166102 · Issue 635942
Zero Downtime Upgrade mechanism updated
Resolved in Pega Version 8.5.4
Scheduled Agents were running several times on each node when there were many executions scheduled for the same agent. This was due to the task derived from the agent's schedule not being unique to the agent, allowing the Zero Downtime Upgrade logic handling the insertion to restart agents several times while reacting to cluster topology changes. To resolve this and make the process more robust, the Zero Downtime Upgrade mechanism has been updated with better tracking and logging.
INC-166398 · Issue 647704
Assistance and diagnostics added for issue with opening imported 'when'
Resolved in Pega Version 8.5.4
After upgrade, attempting to open rules that were developed on lower environments and then imported resulted in unknown errors. A workaround has been added to skip and log any corrupted property that might be interfering with the rule opening: enable Skip-Corrupt-Property to put this in place. To improve diagnostics, the new logger NBA-WME-DEBUG has been added. If the error continues after using Skip-Corrupt-Property, Skip-Corrupt-Property should be disabled and NBA-WME-DEBUG should be enabled and kept active until the issue occurs again.