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-B56373 · Issue 315083

Fixed Correspondence rule contents duplication in Safari

Resolved in Pega Version 7.3.1

In designer studio using Safari, the first content of any correspondence rule was copied and appended to the end of the first line when trying to save a Checkout. This only occurred when a space was added above the existing content, or the same content was copied and pasted into the RTE. This was due to an error in the code used to designate the selection range in CKEditor, and has been fixed.

SR-B56648 · Issue 315674

Added security check when running out-of-the-box reports with ShowSelectorView

Resolved in Pega Version 7.3.1

A security issue was found where non-authorized users were able to access the out-of-the-box report details in their portal by manipulating the URL to pass a "short-cut" parameter that executed the Final "ShowSelectorView" activity. To avoid the need to set the explicit privileges manually, the ShowSelectorView activity will call a security check to prevent this.

SR-B64196 · Issue 315811

Tabindex removed from non-actionable elements for improved accessibility

Resolved in Pega Version 7.3.1

Headers that have no action were focus-able, interfering with accessibility. To fix this, the tabindex has been removed for non-actionable elements.

SR-B64265 · Issue 314375

Tab key navigation focus fixed for Silverlight

Resolved in Pega Version 7.3.1

When using a word merge functionality in the modal dialog with Tab key navigation, after the "Loaded Silverlight" text highlight, the three subsequent tabs did not focus anywhere on the screen. This improper tab movement was caused by missed handling in the pyPegaSilverlight file that caused tabindex to not be properly set for the hidden controls, and has been fixed.

SR-B64661 · Issue 314886

Post-upgrade date/time format change fixed

Resolved in Pega Version 7.3.1

After upgrade, filter values previously shown in date time format were shown in GMT format. This was traced to the class name being returned as empty inside control RRfilter_logic, leading to the Date parameter type being set to empty as well. In order to get className, the ".pyReportDefinition" string will be pre-pended in front of ".className" so the class name will be loaded from the report definition.

SR-B64734 · Issue 315506

Column click focus fixed for >10 column report

Resolved in Pega Version 7.3.1

When there were more than 10 columns in a report, scrolling up to last column and right clicking on it caused the focus to move back to the first column and the window auto-scrolled back to the left. This was caused by right click shifting the focus to left-most, and has been corrected with a code change to handle the proper user agent and pass the event from showMenu.

SR-B64849 · Issue 317182

Sort/Filter alias format accepted for new configurations

Resolved in Pega Version 7.3.1

The Sort/Filter property has to be specified in .property format to sorting and filtering to work; even though it was working during runtime for already implemented properties, validation was not allowing new configuration in this format. This has been fixed.

SR-B65851 · Issue 317197

GenerateMenuAction RUF modified to trim newline strings in windowname

Resolved in Pega Version 7.3.1

While doing development and modification in Designer Studio, some sections were not opening due to the windowname containing newline characters that corrupted the JSON. This has been fixed by updating the pzGenerateMenuAction RUF to trim the strings.

SR-B66139 · Issue 316025

Localization fixed for report name place holders

Resolved in Pega Version 7.3.1

The Report Category Name Place holder was not being localized if it contained special characters. Handling has been added to correct this.

SR-B66153 · Issue 315558

Fixed fr_FR localization for error field value

Resolved in Pega Version 7.3.1

An apostrophe in the translated value in the "This feature is not available in your browser" FieldValue in French was causing JS syntax issues in the pzClientLocaleData HTML rule for gStrFeatureNotSupportedInBrowser variable. This has been fixed by using double quotes instead of single quotes for wrapping variable value.

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