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.

SR-D49537 · Issue 521112

Embedded Pega Chat error resolved

Resolved in Pega Version 8.2.6

A cross-origin frame error was shown when the Pega Chat Window was embedded in a non-Pega page. Investigation traced the issue to code that was accessing the top/parent window, and which failed when used in a mashup scenario. This has been resolved with a try/catch block to wrap the code and handle scenarios where the

SR-D49782 · Issue 518048

Extension point added for ClearInteraction to support custom interactions

Resolved in Pega Version 8.2.6

In order to support clearing a custom interaction page after clicking the "Reset" button on preview console, an extension point has been added to pyClearInteraction.

SR-D57865 · Issue 520963

Added property check for outbound templated email reply

Resolved in Pega Version 8.2.6

When a template was used for the first time for outbound correspondence, email was generated correctly. If the same template was used as the content for reply, the generated email skipped all styles. This was traced to a missing property check, and has been resolved.

SR-D63638 · Issue 544016

Performance improvements for opening cases with embedded images

Resolved in Pega Version 8.2.6

Opening cases containing email interactions was taking an excessive amount of time. This was traced to the use of embedded images, icons, etc, in the message body and signature, and was caused by the pyGetAttachmentsbyCID activity running multiple times due to discussion threads that were duplicated over and over. In some cases, more than 360 calls to the database were seen. This has been resolved by shifting some case opening processes to executing when the listener thread gets the mail, and storing the results in a .pynote property, and a URL will be used to get images instead of embedding them directly to the HTML. If preferred, this can be reverted to the previous behavior by changing the when rule (pyUseCachedHtmlForDisplay) to false.

SR-B51449 · Issue 308503

Property Record localization added for Pega Marketing

Resolved in Pega Version 7.3.1

Localization has been added for Property Record Configuration text in the Pega Marketing application.

SR-B51450 · Issue 308504

Property Record localization added for Pega Marketing

Resolved in Pega Version 7.3.1

Localization has been added for Property Record Configuration text in the Pega Marketing application.

SR-B51450 · Issue 313658

Property Record localization added for Pega Marketing

Resolved in Pega Version 7.3.1

Localization has been added for Property Record Configuration text in the Pega Marketing application.

SR-B51450 · Issue 313738

Property Record localization added for Pega Marketing

Resolved in Pega Version 7.3.1

Localization has been added for Property Record Configuration text in the Pega Marketing application.

SR-B43400 · Issue 307258

Localization added for field value used in 'Enter a Short Description' validation message

Resolved in Pega Version 7.3.1

Localization was failing for the 'Enter a Short Description' validation message when using a Field Value due to the message rule containing spaces. To fix this, a new message rule has been created without spaces in the same ruleset so that it is available for override use in the ruleset.

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