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-B14745 · Issue 285506

pzSUS Param properly URLEncoded

Resolved in Pega Version 7.3

The Tomcat 8+ server was rejecting DWA URLs due to characters such as {,} that it considered to be unsafe. These characters were introduced by pzSus key in the URL, and these values will now be encoded for the browser to resolve these issues.

SR-B15497 · Issue 286469

Styling corrected for last row in tree grid sourced from RD

Resolved in Pega Version 7.3

Tree grids sourced from report definitions had their last row set to the class "grandTotal" instead of "gridRow", causing them to get incorrect styling. This was caused by a missed cleanup for this use case when removing the GrandTotal class from support in RD, and has been fixed.

SR-B15497 · Issue 295707

Styling corrected for last row in tree grid sourced from RD

Resolved in Pega Version 7.3

Tree grids sourced from report definitions had their last row set to the class "grandTotal" instead of "gridRow", causing them to get incorrect styling. This was caused by a missed cleanup for this use case when removing the GrandTotal class from support in RD, and has been fixed.

SR-B15663 · Issue 289919

Trend chart drilldown made consistent with chart display

Resolved in Pega Version 7.3

Trend chart drilldown did not match chart display due to issues with time zone being converted on the chart display but not on the the drilldown. When drilling down into a datetime group, the value of that group was used to create a single filter that matched the group (e.g., "Day of [.DateTime] = 20170101"). This caused the filter to match that time based on the server's time zone settings, not the user's (e.g., if the server was using GMT, then days always began at midnight GMT, so a user could drill down into a single day and get results spanning two days). To correct this, FusionChartDataGeneration.normalizeDateCal no longer localizes for the user's time zone if the time unit is larger than an hour, e.g. day or month units won't be normalized.

SR-B17270 · Issue 288020

XSS filtering added to Autocomplete highlighting

Resolved in Pega Version 7.3

XSS filtering has been added to Autocomplete highlighting for better security.

SR-B1734 · Issue 272443

Added content to blank headers for screen readers

Resolved in Pega Version 7.3

The out-of-the-box report browser previously used a grid where two of the table headers were blank, causing screen readers to not read out these two cells. This has been resolved with the addition of a binary transparent image and an associated tooltip to provide content for screen readers to act upon.

SR-B1734 · Issue 272039

Added content to blank headers for screen readers

Resolved in Pega Version 7.3

The out-of-the-box report browser previously used a grid where two of the table headers were blank, causing screen readers to not read out these two cells. This has been resolved with the addition of a binary transparent image and an associated tooltip to provide content for screen readers to act upon.

SR-B30410 · Issue 294913

Report drilldown works with 'do not display group headings'

Resolved in Pega Version 7.3

When sub-report properties were used in the main reports column source, the report definition displayed the expected results when clicking on a configured drilldown report and chart but displayed no results when listview dataset was clicked. This was traced to having "Do not display group headings" enabled in combination with drilldowns, and has been resolved.

SR-B30713 · Issue 296998

New activity pyCustomValidator added to pzValidateCustomFilterSection

Resolved in Pega Version 7.3

When a report definition enables "Prompt for filter changes before displaying report", and the report specifies a custom filter section, the harness that displays the custom filter section (pzRRDisplayCustomFilterSection) is Final and was not available to validate the fields in the custom filter section. To enable this use, a new available activity "pyCustomValidator" has been added and can be called from pzValidateCustomFilterSection.

SR-B30747 · Issue 297009

XSS filtering added to report browser CategoryDescription

Resolved in Pega Version 7.3

The list of categories on the right in the report browser allowed some HTML tags to be applied when added to the label. XSS filters have been applied to the CategoryDescription labels to improve security.

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