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-B44146 · Issue 300050

Resolved error in adding Association's Page Property in report browser

Resolved in Pega Version 7.3

Adding an Association's Page Property while creating a report in the Report browser generated an error on the screen. This was caused by incorrect passing of the class, and has been corrected.

SR-B45613 · Issue 302956

Fixed query for RD using dependent classes

Resolved in Pega Version 7.3

A runtime exception was generated when running a summary report due to an incorrect query being built for RD when dependent classes was checked. This was caused by pyGetDistinctRecords being set to true even for summary reports, and has been corrected by ensuring pyGetDistinctRecords is set to false for summary reports.

SR-B6161 · Issue 275612

RD generating checkbox control as T/F image fixed

Resolved in Pega Version 7.3

A report definition was not showing checkbox controls as images for true/false properties when generated automatically. This has been fixed.

SR-B6292 · Issue 276738

New accessibility control for adding explicit text to RB column headers

Resolved in Pega Version 7.3

In order to create report browser column headers with explicit text for accessible users, a new available control named pyReportBrowserControl that uses the parameter "Type" has been added to the pzRBShortcutsGrid7 section.

SR-B796 · Issue 283050

Report Definition updated to handle null value field grouping

Resolved in Pega Version 7.3

Report Definitions gave a blank count when grouped by a field with null values. An unnecessary check has been removed from the GenerateGridHTML RUF to correct this issue.

SR-B796 · Issue 277684

Report Definition updated to handle null value field grouping

Resolved in Pega Version 7.3

Report Definitions gave a blank count when grouped by a field with null values. An unnecessary check has been removed from the GenerateGridHTML RUF to correct this issue.

SR-B9137 · Issue 278539

RD column context menu alignment fixed

Resolved in Pega Version 7.3

On a report definition with many columns, scrolling to the right caused the column context menu to not be aligned with the column. The menu alignment code calculations have been modified to correct this.

INC-174116 · Issue 662039

Added reporting on descendant classes for framework

Resolved in Pega Version 8.6.3

Reporting on descendant classes was not working as expected. In a report definition with "Reporting on descendant classes enabled," the framework class and implementation class each refers to two different tables that use the same names but belong to two different schemas. Investigation showed the generated SQL query was not adding the necessary UNION clause, and the records from the descendant classes were missing when running the report on framework class. This was a missed use case and has been corrected.

INC-181684 · Issue 665483

Privileges adjusted for RetrieveReportData

Resolved in Pega Version 8.6.3

In recent versions of Pega, pxRetrieveReportData was secured with @baseclass AllFlows and OpenDeveloperForm privileges. However, this can interfere with setting up roles after update. To resolve this, the privilege restrictions have been removed from pxRetrieveReportData as it is already protected by ABAC/RBAC.

INC-182193 · Issue 674802

Drilldown report takes original report prompt parameters

Resolved in Pega Version 8.6.3

When a report had prompt filters configured and the summary report definition was executed by giving prompt filters, drilling down to one of the records in the summary report display and then looking at the reports displayed and summarized on a column showed a mismatched count. This was found to be a very specific edge case that involved calling the "Summarize" action from a report column within a drilldown report when using a custom filter section and "prompt for filter changes" on the main report. Filters from the custom filter section were being propagated to the drilldown report when summarizing, but the drilled-down-and-summarized report itself had not been refreshed on the client side to reflect this. To resolve this, the actions have been copied from pyDefaultCustomFilterApplyCancel and applied to the Summarize selection in pzGridMenuNavRule.

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