Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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.

INC-231195 · Issue 734205

Additional logging for businessCalendar.CalendarUtility.java

Resolved in Pega Version 8.8

Enhanced logging has been added in order to assist with identifying issues related to the Business Calendar.

INC-232338 · Issue 739258

Data_views Pagination in v2 DX API working as expected

Resolved in Pega Version 8.8

When attempting to use the pagination features available with the v2 DX API '/data_views/{data_view_id}", all results were returned and no pagination was performed. This has been resolved.

INC-RCA-1953 · Issue 716176

ReportStats delete query performance improvements

Resolved in Pega Version 8.8

database connection spike was maxing out the allowed database connections, causing login delays and termination of stream nodes. Investigation traced this to the delete query on pr_log_reportstats, which was a full table scan generated from SQLGeneratorPostgres.purgeTableContainingClass. To improve performance, the full table scan sub-query has been removed and 'limit' syntax has been added to run the necessary deletion in batches.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us