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-185758 · Issue 668962

Optimized GenerateID feature for case creation

Resolved in Pega Version 8.6.2

Enhancements have been added to support high-performance high-volume case ID generation on multiple databases including Oracle , MS-SQL, and Azure.

INC-185760 · Issue 668741

SQL queries modified to use qualified table references

Resolved in Pega Version 8.6.2

Portal launch in the development environment was taking an excessive amount of time, as were some standard reports. The PurgeAssemplyDatabaseCache agent activity also generated an error regarding "(internal.cache.RAPurge) ERROR - Purge, unexpected error in removeOldAppCentricCacheData". These issues were traced to SQL queries that contained pr_sys_app_hierarchy_flat without a schema qualifier, and have been resolved by changing to class qualified table references.

INC-188065 · Issue 671402

Catch added for corrupted alert configuration

Resolved in Pega Version 8.6.2

On creation of a queue processor rule, the alert ID was not present in the logs due to a missing alert configuration page. After this action, the server was not accessible and could not be started. This has been resolved by catching the exception if the alert configuration is malformed or missing.

INC-188405 · Issue 673065

Handling added for SSO servlet name

Resolved in Pega Version 8.6.2

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.

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