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-196415 · Issue 686313

Performance improvements for revalidate and save

Resolved in Pega Version 8.7

In order to improve performance when working with very large numbers of class definitions, an update has been made to optimize the revalidate and save process by avoiding looking up all classes on the system instead using ClassDefinition for existence and checking ancestor data to ensure class is a Rule- or Data- descendant.

SR-A15710 · Issue 236472

Improved BIX extract handling for multiple active agents

Resolved in Pega Version 7.2.1

When multiple agents were scheduled to run extracts at the same time by utilizing pxExtractDataWithArgs, there was intermittent failure in creating the manifest files. The BIX log would not contain an entry for the files being created, no error was displayed, and agents sometimes needed to be restarted. This was an issue with incomplete extraction of the output data and manifest files due to the PAL timer overriding the current thread context as it handled each of the multiple calls. To resolve this, the previous static variables used to store thread and requester instances have been made private to ensure reliability when handling parallel extracts and simultaneous runs.

SR-A16582 · Issue 233320

Improved BIX extract handling for multiple active agents

Resolved in Pega Version 7.2.1

When multiple agents were scheduled to run extracts at the same time by utilizing pxExtractDataWithArgs, there was intermittent failure in creating the manifest files. The BIX log would not contain an entry for the files being created, no error was displayed, and agents sometimes needed to be restarted. This was an issue with incomplete extraction of the output data and manifest files due to the PAL timer overriding the current thread context as it handled each of the multiple calls. To resolve this, the previous static variables used to store thread and requester instances have been made private to ensure reliability when handling parallel extracts and simultaneous runs.

INC-196842 · Issue 683766

APIs updated for sending large attachments with MSGraph

Resolved in Pega Version 8.7

Sending mail using MSGraph was failing with the exception "Error during http request" when attachments were greater than 3MB. This was traced to changes made by Microsoft in the Graph API implementation which caused it to throw a runtime exception instead of the expected 413 status code and relevant message for the attachment size. To resolve this, an update has been made to ensure that any attachment larger than 3MB is sent via the Microsoft Outlook API.

INC-161984 · Issue 638858

Web Tier busy threads released on timeout

Resolved in Pega Version 8.7

Tomcat Web Tier Busy Threads were not being correctly released, causing stability and performance problems that included health check pings not receiving a thread to service the request so the node was marked as bad, users were quiesced, and the node replaced. Investigation showed the 'put' on the blocking queue did not time out when the queue was full and waited indefinitely, keeping the thread blocked. To resolve this, the system will use 'offer' on the blocking queue instead of 'put' to force thread release on timeout. In addition, debug logs have been added to understand when the offer (or Put) does not succeed and the state of the queue that is causing this issue; the debug logs for class com.pega.pegarules.session.internal.serverpush.RoboticAutomationImpl should be enabled only if the thread busy issue is observed and for limited time window while actively debugging.

INC-170599 · Issue 645222

DSS partition count setting made backward compatible

Resolved in Pega Version 8.7

After upgrade, the DSS 'dsm/services/stream/pyTopicPartitionsCount' used to limit the number of partitions was no longer working and instead used the default value of 20. This has been corrected and made backwards compatible.

INC-180479 · Issue 659639

DSS partition count setting made backward compatible

Resolved in Pega Version 8.7

After upgrade, the DSS 'dsm/services/stream/pyTopicPartitionsCount' used to limit the number of partitions was no longer working and instead used the default value of 20. This has been corrected and made backwards compatible.

INC-192078 · Issue 680064

DSS partition count setting made backward compatible

Resolved in Pega Version 8.7

After upgrade, the DSS 'dsm/services/stream/pyTopicPartitionsCount' used to limit the number of partitions was no longer working and instead used the default value of 20. This has been corrected and made backwards compatible.

SR-A22354 · Issue 245861

prpcUtils honors 5.4 compatibility checkbox

Resolved in Pega Version 7.2.1

Pega deployment using prpcUtils was failing due to the 5.4 compatibility checkbox being ignored: the product rule being exported still included schema changes in the exported RAP file. This has been corrected.

SR-A24052 · Issue 248427

Orphaned work objects purged by class

Resolved in Pega Version 7.2.1

Orphaned work objects were not purged when their parent was deleted from the database. To resolve this, selecting a Work- object class for purging will also purge all of the orphans in that class.

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