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.

SR-D33227 · Issue 510825

Check added for lock expiration when using Save for Default locking

Resolved in Pega Version 8.2.5

With the default case locking policy, during the process from creating a Case Object to Submit it was possible for multiple users to edit and save the same work object if the lock expired for the original user. No warnings appeared. To resolve this, handling has been added for a lock expiration scenario: previously, Save for Default locking was not considered. This has now been updated with a check that will evaluate whether or not the lock is gone before attempting to save.

SR-D37779 · Issue 514411

Dynamic System Setting added to Invalidation query to tune performance

Resolved in Pega Version 8.2.5

Running a RuleInvalidation query on an SQLServer database with a large amount of data was causing performance issues. To improve performance, a force order hint has been added which can be enabled with the Dynamic System Setting racache/useForceOrderHintForInvalidationQuery.

SR-D40785 · Issue 515099

WorkPageName preserved during passivation so attachments are correctly tracked

Resolved in Pega Version 8.2.5

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. To resolve this, the data page will be preserved or reloaded as appropriate so the WorkPageName is maintained.

SR-D40883 · Issue 511123

Updated SendEmail shape to remove newline code from the subject line

Resolved in Pega Version 8.2.5

When using the SendEmail shape to send outgoing email, the message contained HTML tags on the subject line that caused it to be split and copied into the email body. This has been resolved by updating PegaEmailClientImpl.prepareMessage() to replace new line characters with spaces in the subject.

SR-D41228 · Issue 512107

DSS added to Request Only Connect SOAP for Robust

Resolved in Pega Version 8.2.5

After upgrade, creating a new SOAP integration set to "Request only" in the Service tab and then running the activity showed requests coming with no response, then failure after three tries. This was traced to previous changes made to support Robust behavior and log failed asynchronous calls, and has been resolved by modifying the Robust support and moving it to a DSS. If “EnableRequestOnlyFaultMapping” is set to “true”, then the ANON_ROBUST_OUT_ONLY_OP option will be used, otherwise, the default behavior will be ANON_OUT_ONLY_OP.

SR-D42406 · Issue 510669

Support added for UTF-8 charset in Connect-REST pyRequestAttachmentPage

Resolved in Pega Version 8.2.5

When using Connect-REST with pyRequestAttachmentPage, Polish characters like "ó" or "ł" were converted to "?". This did not happen when pyRequestAttachmentPage was not used. This was due to the post request body using a multipart handler that ignored the charset being passed in and considered it a respective enum type for Application/json internally instead. This has been resolved by adding support for charset UTF-8.

SR-D42824 · Issue 517010

Warning logged for encrypted email with missing local keystore

Resolved in Pega Version 8.2.5

The Email Listener was becoming stuck while processing encrypted email if the related keystore was not configured within the Pega application. Encrypted mail was not marked as read/deleted, causing the system to attempt to process it again and then repeat the attempt. To address this, a check has been added that will mark the mail as completed for system purposes under this condition, and will log a message to clearly state that the mail was marked as read/deleted but not actually processed due to invalid keystore details.

SR-D43918 · Issue 511182

Resolved duplicate task urgency

Resolved in Pega Version 8.2.5

Duplicate task urgency was displayed when using dynamic layout in non-template mode. Investigation showed that there were three 'when' rules used to display the task urgency based on an urgency value, and two of the 'when' rules were being returned as true, one of which was incorrect. This was due to an incorrect PropertyReferenceImpl object being passed when retrieving the value from the failSafe page because of an incomplete reference, and has been fixed.

SR-D44184 · Issue 511444

ValueList/Group correctly appears on clipboard

Resolved in Pega Version 8.2.5

After upgrade the property of type ValueList/Group was missing from the clipboard. This was traced to an extra 'when' rule applied on the visibility of Layout-2 in final section pzProperty (Pega-Desktop:08-02-01), and has been corrected.

SR-D44215 · Issue 512191

Navigation Breadcrumb honors pyDisplay in navigation link subflows

Resolved in Pega Version 8.2.5

After configuring a sub process (screen flow) inside a screen flow connected by a decision shape having a fork condition, the Navigation breadcrumb for this subprocess was always visible irrespective of the connector when condition. This was traced to pyDisplay not being considered for subflows while building navigation links, and has been resolved.

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