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.
INC-166631 · Issue 637023
Default for 'database/oracle/allowOptimization' set to false in patches
Resolved in Pega Version 8.5.4
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-169055 · Issue 644760
Performance improvements for database queries and archiving
Resolved in Pega Version 8.5.4
In order to improve the performance of database queries, repetitive unnecessary database calls have been removed, archival queries have been simplified, and diagnostic metrics were added. Optional batch requestors have been added to all archival services with their own DSS settings to allow processing more cases in parallel. It is recommended to create 2 additional indexes to help with the archival process. The indexes will be on:pegadata.pr_metadata (pyisparent, pyobjclass, pyarchivestatus) INCLUDE (pyinskey); pegadata.pr_metadata (pyisparent, pyarchivestatus) INCLUDE (pyinskey);
INC-169518 · Issue 649156
Email address parsing logic updated
Resolved in Pega Version 8.5.4
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 645805
Decision table query performance improvements
Resolved in Pega Version 8.5.4
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-170599 · Issue 645223
DSS partition count setting made backward compatible
Resolved in Pega Version 8.5.4
After upgrade, the DSS to limit the number of partition counted was no longer working and instead used the default value of 20. This has been corrected and made backwards compatible.
INC-170620 · Issue 651804
Handling added for RuleNotFound exception
Resolved in Pega Version 8.5.4
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-170669 · Issue 651810
Handling added for RuleNotFound exception
Resolved in Pega Version 8.5.4
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.