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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-177470 · Issue 657142

Optimization prconfig check added for TableInformationMap

Resolved in Pega Version 8.7

A prconfig setting check has been added to the TableInformationMap use of OPTIMIZE_SMA_QUERY during its foreign key lookup.

INC-177737 · Issue 663141

Authentication requirement updated for CallConnector

Resolved in Pega Version 8.7

After update, invoking a REST API call during SSO login which eventually called pxCallConnector (Final Activity) in @baseclass Pega-RulesEngine failed at the CallConnector step. This was caused by a change in recent Pega versions which enabled authentication for this activity, and has been resolved by marking the activity as internal and disabling the authentication requirement.

INC-177773 · Issue 665338

Tracer protections updated

Resolved in Pega Version 8.7

Cross-site scripting protections have been updated for Tracer.

INC-177993 · Issue 657200

Archival IndexManagerService performance improved for very large tables

Resolved in Pega Version 8.7

Archival IndexManagerService was taking an excessive amount of time to run updateStatusForCasesWithInconsistentArchiveStatus(), a method which checks the parent case's archival status and compares it to all its children (cases & dependencies) statuses and flags parent cases with statuses that do not match. This check is done on all parent case instances that are in the indexer stage, and intermittently timed out and failed on a pr_metadata table containing over 5,000,000 records. This has been resolved by splitting the inconsistent check into smaller tasks and addressing potential parent/child/dependency relationships that can occur in the pr_metadata table.

INC-178148 · Issue 660924

Handling added for SSO servlet name

Resolved in Pega Version 8.7

After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.

INC-178923 · Issue 660885

Resolved startup error related to business calendar object

Resolved in Pega Version 8.7

An error recorded in the log file when the server started was traced to a cache update that removed the old business calendar object and added the new business calendar object to the business cal list. This has been resolved by updating the system to replace the business calendar object instead of removing the old one from the cache first.

INC-179025 · Issue 665546

Null check added for getTargetNodeUUID

Resolved in Pega Version 8.7

A null pointer error was seen from the tracer during a security scan. This has been resolved with the addition of a null check for TracerRequest.getTargetNodeUUID.

INC-179106 · Issue 662617

Null data page check added for DataPageTelemetryImpl

Resolved in Pega Version 8.7

Recent work was done to modify the StreamChangeTracker trackValueChanges API to return false when invoked for properties of mode page. An additional null check has been added in DataPageTelemetryImpl.recordDataPageLoaded to handle a null pointer exception caused by null data page definitions.

INC-179167 · Issue 659590

Atmosphere update

Resolved in Pega Version 8.7

The Atmosphere jar has been updated to version 2.4.5.9.

INC-179448 · Issue 676270

Tracer protections updated

Resolved in Pega Version 8.7

Cross-site scripting protections have been updated for Tracer.

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