INC-163863 · Issue 632424
Monthly agents run correctly on non-English locales
Resolved in Pega Version 8.4.5
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 635144
Class mapped to CustomerData is incrementally indexed as expected
Resolved in Pega Version 8.4.5
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 638637
Java object type removed from pyStream to resolve GetFile class error
Resolved in Pega Version 8.4.5
It was not possible to perform Property-Set on pyStream(java.io.InputStream) to assign it with another object of type(returned by pxGetFile Rule-Utility-Function). 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 634408
UseNoCacheHeaders default expiration set to "0"
Resolved in Pega Version 8.4.5
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-164472 · Issue 635111
Performance improvements for archiving and purging
Resolved in Pega Version 8.4.5
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-164526 · Issue 641165
Unneeded ShowContext rules removed
Resolved in Pega Version 8.4.5
The following unused rules are obsolete and have been withdrawn:RULE-OBJ-ACTIVITY SYSTEM-REQUESTOR-CONTEXT SHOWCONTEXTMANAGER RULE-OBJ-HTML SYSTEM-REQUESTOR-CONTEXT REQUESTORCONTEXTMANAGER
INC-166631 · Issue 637020
Default for 'database/oracle/allowOptimization' set to false in patches
Resolved in Pega Version 8.4.5
Recent patches contained an Oracle query optimizer implemented to prevent performance problems and other known Oracle bugs from impacting environments. However, while these changes were well intentioned, they either required providing additional database privileges or adding some configuration changes to provide the information needed in lieu of the privileges. This does not conform to the expected patch experience. To remedy this issue, the optimizations have been switched to being disabled by default in this release so that the behavior on upgrade is the same as prior to the applied patch release. If Oracle performance issues are seen, it is possible to enable the optimizations and provide either the needed privileges or configuration to make use of them. Please note the default remains 'enabled' for Pega 8.6.
INC-167141 · Issue 643510
Updated nextRunTime to handle report scheduled during daylight savings time change
Resolved in Pega Version 8.4.5
A job scheduled to run at 2AM every night executed continuously during the Daylight-Savings Time change between 1AM and 2AM EST. This has been resolved by updating nextRunTime so that it will not shift the execution time by the daylight saving time offset if the following nextRunTime is not in daylight time.
INC-168959 · Issue 643514
Updated nextRunTime to handle report scheduled during daylight savings time change
Resolved in Pega Version 8.4.5
A job scheduled to run at 2AM every night executed continuously during the Daylight-Savings Time change between 1AM and 2AM EST. This has been resolved by updating nextRunTime so that it will not shift the execution time by the daylight saving time offset if the following nextRunTime is not in daylight time.
INC-169518 · Issue 649157
Email address parsing logic updated
Resolved in Pega Version 8.4.5
Email listener functionality for case creation and email notifications was not working as expected after update due to a difference in the the service email rule request header properties (pyInboundEmail.pyFrom & .pyInboundEmail.pyFromDisplayName) clipboard values. This has been resolved by updating the parsing logic for the email addresses to look for an InternetAddress object and then fallback to a regex match.