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.
INC-169764 · Issue 645806
Decision table query performance improvements
Resolved in Pega Version 8.4.5
Severe latency was seen after upgrade, and it was not possible to save business rule changes. This was traced to an issue with the decision rule being treated as a custom rule, and has been resolved by inserting a check. In addition, optimization has been added for queries on the pr_sys_decchg table.
INC-170551 · Issue 656561
Rule Assembly update for pxTextInput and pxDisplayText
Resolved in Pega Version 8.4.5
After the application restart, multiple rule assembly alerts were seen for pxTextInput and pxDisplayText . During first access, Assembly is done and container is cached in VTable; investigation showed that in this case, the Load class without the package name had a class not found issue, and then subsequent access tried to use the container from cache and assembly was not done. To prevent this, an update has been made to perform the class lookup using the package name and class name.
INC-170669 · Issue 651811
Handling added for RuleNotFound exception
Resolved in Pega Version 8.4.5
If a declare rule was run on a redux page and the highest ruleset version was withdrawn, a RuleNotFound exception was thrown and step status was set with the message "Failed to find a 'RULE-DECLARE-EXPRESSIONS' ...". This has been resolved by updating the system to avoid throwing a RuleNotFound exception if the candidate list is empty for the declare expression.
INC-170883 · Issue 649997
Race condition resolved for input/output pipe streams
Resolved in Pega Version 8.4.5
Writing to S3 using file data set was failing with the error "Exception occurred while uploading file". The system was relying on PipedInputStream for getting the data from the file while uploading, which needs to be connected to PipedOutputStream which holds the data to be uploaded. Investigation showed a race condition was occurring where for some use cases the reading of inputStream was happening before the connection of I/P and O/P streams, resulting in a "Pipe not connected" error. This has been resolved.
INC-170950 · Issue 652330
Handling added for datetime set by relative reference
Resolved in Pega Version 8.4.5
When initializing a datetime property contained within .pxPages() in a data transform rule, if the property being set applied to @baseclass it was initialized as decimal string while all other properties were handled as normal GMT-based Pega date time strings. Investigation showed that the decimal value was set when the target page was given by a relative reference like .pxPages(TEXT) which was also defined on Pages & Classes. This has been resolved with an update to detect relative reference as page name in Pages & Classes tab and fall back to the old assembler.
INC-171230 · Issue 650333
MSGraph email listener enhancements
Resolved in Pega Version 8.4.5
Attachments with .eml /.msg extensions were treated as FileAttachments by the MS Graph API and generating a classcastexception. To resolve this, a check has been added to identify the attachment along with content type so .eml will be correctly recognized. In addition, the MSGraph email listener functionality related to converting from Graph to MIME message has been enhanced around the 'TO' and 'CC' recipients in a MIME message and for parsing nested attachments in Item attachment for addition to MsgraphMessage.