INC-226764 · Issue 745051
Performance improvements for save-as
Resolved in Pega Version 8.8
Performance issues were seen when using save-as for rules such as Declare expression, When rules, activity, etc. This was traced to a very large number of extra database queries that were being executed while building the Declarative Cache. To resolve this, an update has been made so the queries used for the Declarative Cache will only be executed when required.
INC-226830 · Issue 727154
Case Archival hierarchy updated for multiple occurrences of a child case
Resolved in Pega Version 8.8
Case Archival did not correctly discover hierarchy when child case appeared multiple times in the hierarchy. This was due to the CaseAssociationsProvider class having a check to skip performing the discovery when the case type had already been processed, and has been resolved by updating the handling for this scenario.
INC-227988 · Issue 736463
Corrected unnecessary declare trigger firing
Resolved in Pega Version 8.8
The crmAuditStage declare trigger was activated whenever the views mentioning the properties were accessed even though the values for the mentioned properties were not changed or updated. This resulted in a row inserted in the audit table. The audit data was in turn read by other processes to determine the age, health status of opportunity, etc, causing several reporting issues. To resolve this, if the target and source pages have the same property(same value), while invoking the Page-Merge-Into with Keep value 3(PUTALL_MERGE), then it will not create changeElements and the Declare Trigger and Declare On Change Rules should not fire unnecessarily.
INC-228622 · Issue 739122
Month names localized correctly for "CZECH"
Resolved in Pega Version 8.8
Localization for the country "CZECH" has been updated to correct the month names displayed in calendar control.
INC-229608 · Issue 732636
UpdateDateTime casing corrected in filters
Resolved in Pega Version 8.8
When using Job Scheduler with MS/SQL, the error "Cannot find either column 'mktdata' or the user-defined function or aggregate 'mktdata.pr_read_from_stream', or the name is ambiguous." This was traced to a casing issue and has been resolved by updating the pxupdatedatetime property to pxUpdateDateTime in Filters F1 and F2.
INC-229907 · Issue 734305
SOAPAppenderPega includes namespace in ClusterName and Signature fields
Resolved in Pega Version 8.8
After update, the Predictive Diagnostic Cloud (PDC) was not not logging the events, servers status, etc, and was indicating it was blocked by the IBM DataPower Gateway due to the SOAP message format. This was traced to the namespace not being included in the ClusterName field, and has been resolved by updating the sendEvent method in SOAPAppenderPega.java to add the namespace to the ClusterName and Signature fields in the header.
INC-229921 · Issue 738629
Corrected duplicate repository delete request
Resolved in Pega Version 8.8
The delete request to remove a document from the repository was duplicated. This was caused by the 'pzDeleteFromRepository' activity instantiating the D_pxDelete in its own thread and then again in the current thread due to the D_pxdelete data page being loading asynchronously, and has been resolved by making the calling activity synchronous when loading the data page.
INC-229930 · Issue 739980
Corrected duplicate record error message
Resolved in Pega Version 8.8
When inserting a duplicate record in a grid, the error was shown at the harness level instead of the record level. This was traced to the error messages being removed from the step page, and has been resolved by updating the system so messages will not be cleared if the same value is being set.
INC-229992 · Issue 735014
SOAP TLS version will be dynamically set
Resolved in Pega Version 8.8
Using the "Create SOAP connection" wizard resulted in an error no matter what WSDL was imported. The original implementation of the SOAP wizard relied on a hard-coded TLS level when invoking the HTTP call to the WSDL URL. The hardcoded value was never updated past TLSv1, and had to be manually updated by developers for new TLS versions. This was insufficient when the WSDL URL provided did not support lower TLS versions. To resolve this, the logic has been updated to source the TLS version from the system setting "Pega-IntegrationArchitect pyLowestAllowableTLSVersion", which will match the generated rules and stay up to date as Pega security standards update. The value will default to v1.2 if the system is unable to get a value from setting. To make the best use of this, do not use hardcoded values for version specification in dynamic flows where possible.
INC-230929 · Issue 743824
Corrected memory leak related to CLOB cleanup
Resolved in Pega Version 8.8
Excessive CPU use was seen even under normal traffic. Investigation identified an edge case where CLOBs were not all being cleaned up, causing memory leakage. This has been resolved by ensuring unused objects are freed.