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.

SR-D40785 · Issue 515100

WorkPageName preserved during passivation so attachments are correctly tracked

Resolved in Pega Version 8.4.2

When a work object was left open but inactive for a period, using the delete button in the pyAttachFieldRequired section caused the deletion of the Attachment Links for the 500 most recent attachments in the system with the same value for the AttachmentFieldName, regardless of which work object they were attached to. This was due to the delete attachments activity being executed with missing parameters: since data page loading was disabled and read-only data pages are not passivated, the value for the autopopulate property 'WorkPageName' was passed as empty. This has been resolved.

SR-D71369 · Issue 559180

Resolved NullPointerException during passivation

Resolved in Pega Version 8.4.2

NullPointerExceptions were seen in the logs. This was traced to the BLOB becoming corrupted during passivation, and the code has been updated to resolve this issue.

SR-D74921 · Issue 551789

Error condition will close WebSocket connection

Resolved in Pega Version 8.4.2

An async listener has been added that will close the WebSocket connection when an error condition is encountered.

SR-D81911 · Issue 553095

Reference property copying updated

Resolved in Pega Version 8.4.2

An error appeared on screen when performing the local action "NonProceed case" after upgrading. This was traced to the way copying reference properties was handled as part of pxDeleteAssignmentsForWork, and has been corrected.

SR-D83424 · Issue 552724

Class Loader cache values wrapped with WeakReference for improved cleanup

Resolved in Pega Version 8.4.2

Out Of Memory exceptions due to Metaspace were observed on Web tier instances running with a max Metaspace size of 2GB. Investigation showed that in PRClassLoaderDB, mLoaderCache values were wrapped with a SoftReference. To resolve this, the Class Loader cache values will be wrapped with a WeakReference, allowing the cache to free memory when it is no longer needed. JVM options has also been added to switch types of References being used if there is a preference.

SR-D87605 · Issue 547298

Indexes and tables updated to improve purge query performance

Resolved in Pega Version 8.4.2

Due to work done previously, purge queries to clean up the application ruleset index and application hierarchy_flat tables were running slowly or not returning the expected results. This has been resolved.

SR-D88813 · Issue 556090

Resolved getDatabaseIndices release

Resolved in Pega Version 8.4.2

While retrieving the indexes of the database, the result sets were not closed, leaving the cursors open as well. Eventually the number of open cursors exceeded the database max, preventing any further database operations. This has been resolved by appropriately releasing the cursors after finishing with them, preventing the failure.

SR-D89835 · Issue 554303

Updated padding character handling for access group hash

Resolved in Pega Version 8.4.2

While generating an access group hash from an access group name, Pega was using the '(' character as padding. However, Siteminder blocks the '(' character, causing requests to be rejected. To resolve this, the padding character will be removed while encoding and decoding will handle hashes both with and without the padding character.

SR-D91362 · Issue 556048

Updated handling for redirect location header

Resolved in Pega Version 8.4.2

After upgrade, browser refresh/reload was not working, instead displaying a grey screen with no error in Google Chrome and a 404 message in Microsoft Internet Explorer 11. Investigation showed this was due to a redirect request being sent without location header; this was caused by the pageToCopy thread being reused in the redirect even though it was null, resulting in the location header not being populated in the requestor page. To resolve this, the system has been updated to skip copying the pages and set then location header if the thread is the same.

SR-D91894 · Issue 557222

Class Loader cache values wrapped with WeakReference for improved cleanup

Resolved in Pega Version 8.4.2

Out Of Memory exceptions due to Metaspace were observed on Web tier instances running with a max Metaspace size of 2GB. Investigation showed that in PRClassLoaderDB, mLoaderCache values were wrapped with a SoftReference. To resolve this, the Class Loader cache values will be wrapped with a WeakReference, allowing the cache to free memory when it is no longer needed. JVM options has also been added to switch types of References being used if there is a preference.

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