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-A17223 · Issue 238044

Fixed JS error for Date Calendar changes

Resolved in Pega Version 7.2.1

Using Microsoft Internet Explorer, the Date Calendar was intermittently throwing a JavaScript error when trying to select another date from the date picker. This was caused by the rapid changing of dates overwhelming the onChange refresh section configured on the date input and leaving a stale input element, and has been fixed.

SR-A17403 · Issue 236170

Microsoft Internet Explorer browser check added to screenshot tool

Resolved in Pega Version 7.2.1

When closing an Microsoft Internet Explorer browser tab with an interaction open, an error is generated relating to the create snapshot tool. This screenshot functionality is only supported in Microsoft Internet Explorer8 and Microsoft Internet Explorer9, and a browser check has been added.

SR-A17411 · Issue 234053

Alignment resolved for repeating grid headers

Resolved in Pega Version 7.2.1

Headers were mis-aligned in the UI Gallery for a repeating grid when the freeze header option was chosen along with pagination and width of the content. This was an issue with the initScrollbars function, and has been corrected.

SR-A17476 · Issue 234924

Autocomplete working on node level data pages

Resolved in Pega Version 7.2.1

The auto complete feature was not working if the Categorize search results option was checked on node level data pages. The SortClipboardData now has support for node level data pages categorization.

SR-A17488 · Issue 234010

Corrected truncation of localized text in Report Viewer filters

Resolved in Pega Version 7.2.1

The localized test "Select Values" text was being truncated in the Report Viewer filters were enabled. This setting has been updated to take the additional width without truncating.

SR-A17497 · Issue 234925

Enhanced column supports in 'Export to Excel'

Resolved in Pega Version 7.2.1

Reports using functions in columns were not working with 'Export to Excel'. This has been fixed. Support has also been added to display all the report column localized values in pzListViewExcelData while doing Export to Excel: Simple Column, Joins, Declare Index, Associations, Sub Report, Functions and Embedded Properties.

SR-A17672 · Issue 236191

Tab layout groups updated to retain status when switching

Resolved in Pega Version 7.2.1

Switching between tabs caused the harness to refresh. The tab layout groups have been updated to ensure expected behavior.

SR-A17683 · Issue 235082

Autocomplete JSON error resolved

Resolved in Pega Version 7.2.1

A JSON parse error was causing issues with autocomplete controls after updating. This was caused by a syntax error, and has been corrected.

SR-A17881 · Issue 233850

Browser check added to TextArea for consistent rendering

Resolved in Pega Version 7.2.1

When using the Google Chrome browser, an Enter key press / newline was calculated as two characters during rendering but as a single character in the character counter. This would cause the Text Area to behave differently depending on the browser. To avoid rendering issues, a check has been added to compensate for this difference.

SR-A17916 · Issue 234503

NPS Report drilldown filters corrected

Resolved in Pega Version 7.2.1

The recent changes to the NPS Report drilldown activity to call pzUpgradeOnOpen data transform have been further refined to correct a filtering error. When the filters were upgraded using the pzSetFilterDataType data transform, the value of the pyIsLeftOperandAFunction property was not appropriately set to true/false (depending on the value of the filter). This led the drilldown to incorrectly think that the column was a property instead of a calculation if the calculation used nested calculations, and has been resolved.

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