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-C2850 · Issue 348798

Missing buttons returned to Marketing report browser

Resolved in Pega Version 7.4

After upgrade, the Report Browser in the Pega Marketing portal was missing the 'Add Category' and 'Add Report' buttons. This was due to a difference in the UI-kit for the header, and has been fixed.

SR-C2920 · Issue 344845

Summary report count fixed when using filter prompt

Resolved in Pega Version 7.4

The summary data count was not getting updated in a report unless the "Prompt for filter changes before displaying report" option on Report Viewer tab (Actions -> Refresh) was unchecked. This was an error in the refresh code related to the display prompt filter check and has been corrected.

SR-C9779 · Issue 351372

Performance improvement for data page sourced by RD

Resolved in Pega Version 7.4

Performance improvements have been made to using a Data page sourced by a report definition by removing the step that creates an unneeded parameter page.

SR-B69751 · Issue 325146

Resolved button select error in PegaSurvey

Resolved in Pega Version 7.4

In Pega Survey, the 'Simple Question' with 'Answer mode' of 'RadioButtons' was not working properly: selecting one radio option via mouse click caused another radio option to be selected after the buttons were clicked multiple times. This was traced to legacy code which required an extra refresh in SurveyScripts for a Survey smart shape. This code has now been removed as it is not required in QuestionScripts.

SR-B14783 · Issue 291708

Added image retrieval support to correspondence rule

Resolved in Pega Version 7.4

If images were present in the correspondence rule used to send emails, no images were visible in the emails sent out from Pega after restart. This was traced to 'SendEmailNotification' using the 'StaticContentUtilsImpl.getResolvedFile(String)' engine API to fetch the Image bytes, which did not have the necessary support to fetch 'Data-Content-Image' content. This has been added.

SR-B74711 · Issue 328307

Added image retrieval support to correspondence rule

Resolved in Pega Version 7.4

If images were present in the correspondence rule used to send emails, no images were visible in the emails sent out from Pega after restart. This was traced to 'SendEmailNotification' using the 'StaticContentUtilsImpl.getResolvedFile(String)' engine API to fetch the Image bytes, which did not have the necessary support to fetch 'Data-Content-Image' content. This has been added.

SR-B84855 · Issue 339079

Clarification on DSN Thread Topic parsing

Resolved in Pega Version 7.4

The PDN article regarding parsing DSN emails incorrectly stated that "If the message triggers a DSN, the Thread-Topic value is still intact. You can map the value from this header to a utility named parseThreadTopicHeader in the Message Header section on the Request tab. Be sure to specify the pyInboundEmail page property in the Map To Key field." In actuality, the Thread topic is not intact for all domains; it depends on the email provider. If the thread topic is not present in the DSN mail header, custom logic will need to be added in the email service activity rule to get it from the mail content.

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