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-C7762 · Issue 350154

Commas removed from filter values to resolve validation errors

Resolved in Pega Version 8.1

When using a Grid layout configured in a section rule, clicking the Filter option and entering a comma separated value in the "To" field in a decimal-type column resulted in an "Invalid numeric range" option message. No error was seen if comma separated values were entered in both the "To" and "From" fields. Because the checkRangeFilter() function in ui_grid.js uses parseFloat() API to extract the decimal content entered in the search boxes, decimals after commas are ignored and validation failed due to the fields not matching. This issue has been fixed by implicitly removing any commas entered by the user.

SR-C928 · Issue 343908

True/false values localized in report filters

Resolved in Pega Version 7.4

Localization has been added to the labels of grid Section pzAvailableValues.

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.

SR-B96972 · Issue 343423

Specification rule save-as loads requirements

Resolved in Pega Version 7.4

While doing 'Save As' of a Specification rule from a locked ruleset version to a higher unlocked version of the ruleset, the linked Requirements were not shown in the Requirements section under the Details tab. Sometimes a refresh would show the requirements, but intermittently an exception would be generated. This was traced to the system not auto-populating the requirements list on 'save as' of the specification, and code has been added to PostActionSaveAs of the 'Rule-Application-UseCase' class to populate the Requirements link on 'save as' of this rule.

SR-B90037 · Issue 340248

pyFolderID honored for SaveFileContent

Resolved in Pega Version 7.4

After customizing the out-of-the-box Activity "SaveFileContent" by setting the property "pyFolderID," all attachments were stored in the Documentum root folder instead of the specified folder. This was traced to a code error that bypassed setting the parameter, and has been fixed.

SR-C1910 · Issue 344160

Performance improvement for D_StartingFlows

Resolved in Pega Version 7.4

The algorithm for loading D_StartingFlows has been adjusted to be specific to when "optimistic packaging" is enabled, so that D_StartingFlows is not loaded during typical delta sync response generation.

SR-C496 · Issue 343628

Images render correctly in iOS/Android

Resolved in Pega Version 7.4

The mobile app was not rendering images on IOS or Android devices, but the images were visible when running the mobile view from a desktop browser. In addition, the vertical scroll bar was not displayed on lengthy screens. This was due to the template code not appending '+xml' to MIME type when the SVG content did not start with "<?xml ," and has been fixed by always concatenating +xml in IconAssembly.java.

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