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-202878 · Issue 713792

Handling updated for social messaging items with very large embedded images

Resolved in Pega Version 8.6.5

Job scheduler was running out of memory while handling large/multiple files, causing nodes to crash while handling Social Messaging items. Inline images were also not being sent in the ACK email. Investigation traced this to a custom job scheduler and activity used to create PDFs from email communication and send the PDFs to a third-party system. This used the standard Email Triage/PegaSocial functionality for the emails, which were stored as instances of PegaSocial-Message. The custom Job scheduler and activity then leveraged the Data Page D_pxEmailPosts to retrieve the emails in order to harvest the text from the emails. The issue occurred when a number of the emails had multiple or large embedded images in them, meaning the PegaSocial-Message instances are very large. This resulted in the node running out of memory and crashing. To resolve this, code has been added to support inline images in ACK email and the complete message from Pulse will be used instead of the original message as the email body for the ACK email.

INC-211974 · Issue 706616

UpgradeInteractionCase modified to update work page on save

Resolved in Pega Version 8.6.5

After update, service cases were failing to unpend when using a custom data transform that accessed the D_CorrespondenceCase data page. Investigation showed the D_CorrespondenceCase data page was internally using the D_pxGetInteractionCaseDetails data page; this call upgraded and saved and committed the case but this commit released the lock which the custom data transform had acquired. Because this happened before accessing the CorrespondenceCase datapage, it led to an error while committing the service case details. To resolve this, the postprocessing activity "pyUpgradeInteractionCase" of D_pxGetInteractionCaseDetails has been modified to write the update on the work page as soon as a save is performed.

INC-191412 · Issue 692674

Large Data page join condition available for Mobile

Resolved in Pega Version 8.6.5

Support for a join condition has been added to the Large Data page for use in Mobile to match the use available on desktop.

INC-198193 · Issue 723624

Error correctly shows for each attempt to upload an oversize file

Resolved in Pega Version 8.6.5

The error message indicating an uploaded file exceeded the permitted file size was only shown on the first try on Android. Subsequent attempts to upload the same oversize file did not generate any error. This was due to a persisting value, and has been resolved by explicitly clearing the input value for the mobile browser upload.

INC-205683 · Issue 702561

Data transform actions supported in offline app

Resolved in Pega Version 8.6.5

Support has been added for pre- and post-processing data transform functionality and validation in the local actions of the offline app.

INC-222126 · Issue 721903

Improvement for mobile display error related to harness timing

Resolved in Pega Version 8.6.5

After updating from 8.1 to 8.6, working very quickly on mobile to create a case and refresh it resulted in a "Display error" screen that included the message "Failed to find instance @baseclase.pyCreate of type Rule-HTML-Harness". This was caused by the system not being initialized with the needed content and some target parameters therefore being evaluated as null. A preliminary fix for closeDocCallback when WebView is not loaded has been added which has significantly reduced the frequency of this issue. Additional work will be done towards a complete resolution in a future release.

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