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-127591 · Issue 564818

isAuthenticated checks trimmed for Performance Improvement

Resolved in Pega Version 8.2.7

In order to improve performance, a duplicate check of pxIsRepositoryAuthenticated has been removed from the Function Rule.

INC-127859 · Issue 564619

Email image retrieval switched to Lazy Load

Resolved in Pega Version 8.2.7

In email, multiple images being loaded at once resulted in a performance impact. To resolve this, the fetching of inline images has been modified to use Lazy Load optimization which will retrieve file content from S3 storage on a need basis.

INC-127891 · Issue 564726

Added check for redirects when getting images from S3

Resolved in Pega Version 8.2.7

When retrieving images from S3 storage, a 303 redirect status response code was shown. Investigation showed that using a public URL caused the redirects, and this has been resolved by adding an AG hash while fetching images via an activity.

SR-D87412 · Issue 563227

Support added for multi-language email parsing

Resolved in Pega Version 8.2.7

Parsing an email body for different languages was causing performance issues. To resolve this, an enhancement has been added to support email IVA in seven languages, to use this, override the Work-Channel-Triage.pyParseReplyMail activity and add the required languages in the given parameter.

SR-D90459 · Issue 552661

Improved handling for attachments not using UTF-8 encoding

Resolved in Pega Version 8.2.7

When an email was received that used a charset encoding other than UTF-8, special characters in the HTML body were not displayed and instead the replacement character was shown. To resolve this, the system will read the encoding from the email rather than use the meta tag, and will add the attachment's HTML encoding information in Data-WorkAttach-File so that the same can be used to process and display the original HTML properly.

SR-D92688 · Issue 551340

Optional feature to improve pxETReport performance

Resolved in Pega Version 8.2.7

Poor performance was seen when using pxETReport. This was caused by the system loading the recent cases widget by looking up all the ET cases within last 30 days, opening each ET case to check if it is from the same pyFrom email address, and then if yes, opening its related service case. On a complex system, this was potentially a slow process. To improve performance, the "Related cases" feature can now be disabled through an overridable 'when' rule.

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