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-176903 · Issue 664988

Ready to process records count correctly displayed

Resolved in Pega Version 8.5.5

After update, the QP's ready to process records count was always shown as zero in the Admin studio QP landing page. This was traced to a missing sListMaxResultCount property in the SQL query for qp-partition retrieval; this has been added, and the default value has been changed from 0 to -1 for proper interpretation of results.

INC-177773 · Issue 665336

Tracer protections updated

Resolved in Pega Version 8.5.5

Cross-site scripting protections have been updated for Tracer.

INC-177993 · Issue 657199

Archival IndexManagerService performance improved for very large tables

Resolved in Pega Version 8.5.5

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 660926

Handling added for SSO servlet name

Resolved in Pega Version 8.5.5

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 660887

Resolved startup error related to business calendar object

Resolved in Pega Version 8.5.5

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 665544

Null check added for getTargetNodeUUID

Resolved in Pega Version 8.5.5

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-179167 · Issue 659592

Atmosphere update

Resolved in Pega Version 8.5.5

The Atmosphere jar has been updated to version 2.4.5.

INC-179448 · Issue 664314

Tracer protections updated

Resolved in Pega Version 8.5.5

Cross-site scripting protections have been updated for Tracer.

INC-182572 · Issue 663555

Support added for multiple host proxy architecture

Resolved in Pega Version 8.5.5

When using an architecture where certain types of users were sent through multiple proxy servers to get the Pega Cloud instance, an exception was generated at the point of accessing the environment. This was traced to the use of Apache 2.4 with mod_proxy. As the request passed through each proxy, the x-forwarded-host header had values appended to it by mod_proxy which resulted in the error "com.pega.pegarules.pub.context.PRSecurityException: Multiple host names in header X-forwarded-Host". This has been resolved by updating the code to support using a multiple host proxy configuration.

INC-184668 · Issue 665956

Check added for null mColumn values while estimating size

Resolved in Pega Version 8.5.5

A null pointer error indicating an issue with AbstractDataPageHandler.estimateDataSize was traced to missing handling for null values in mColumns while calculating size. This has been resolved with the addition of a null check.

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