Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

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 SR ID number in order to find the associated Support Request.

INC-135719 · Issue 580692

Corrected reference exception for filter on a grid sourced from a parameterized report definition

Resolved in Pega Version 8.3.6

An Invalid Reference Exception was thrown after attempting to apply a filter on a grid sourced from a parameterized report definition. This was traced to work done to allow cross-scripting filters to allow filters to contain special characters, and has been resolved.

INC-131942 · Issue 574322

Orphaned CSS reference removed from DisplayReport harness

Resolved in Pega Version 8.2.8

An intermittent invalid CSS error was appearing in the DisplayReport harness when an operation resulted in the regeneration of the harness content. This was traced to a reference to the workform_pyReportingSkin CSS, which was used in old reporting features and is not in use anymore. The reference has been removed to resolve this issue.

INC-135719 · Issue 580689

Corrected reference exception for filter on a grid sourced from a parameterized report definition

Resolved in Pega Version 8.2.8

An Invalid Reference Exception was thrown after attempting to apply a filter on a grid sourced from a parameterized report definition. This was traced to work done to allow cross-scripting filters to allow filters to contain special characters, and has been resolved.

INC-140110 · Issue 600399

Large filter values accepted in Report Definition edit

Resolved in Pega Version 8.2.8

Report definition edit filter values were not accepting large comma separated values properly. This has been resolved by modifying the logic in RRFilters_Logic to use ReportFilter.getReportFilters.

INC-143191 · Issue 596470

Scheduled tasks landing page shows all tasks

Resolved in Pega Version 8.2.8

Due to pzGetScheduledTasks listview having a hardcoded limitation of 500 records to be fetched, not all scheduled tasks were being shown in the scheduled tasks landing page. This has been resolved by modifying the pyCreateSummary activity to use a newly created Report Definition to fetch data instead of list view.

INC-144756 · Issue 602724

Security improved for searches

Resolved in Pega Version 8.2.8

Authentication requirements have been added to activities associated with searching.

INC-120343 · Issue 573075

Explicit parent added for descendants in subreport to correct summary

Resolved in Pega Version 8.2.8

When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.

SR-D90400 · Issue 563185

Explicit parent added for descendants in subreport to correct summary

Resolved in Pega Version 8.2.8

When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.

INC-149143 · Issue 613140

Report category error messages made accessible

Resolved in Pega Version 8.3.6

In order to improve accessibility while creating new reports, labels have been added to the error messages on the category name field.

INC-151568 · Issue 610219

Handling added for comma value in FusionCharts XML

Resolved in Pega Version 8.3.6

After creating a Summary Report through the report browser and adding that report to the Dashboard, clicking on the report to drill down generated the error "Can't open the rule with the specified keys". Investigation showed that if a category or series in a Report Definition chart contained a comma, the drilldown would not work because of an incorrect pyclassname being passed. This was traced to the use of XML to configure the chart: the FusionCharts third-party library parses the link XML incorrectly and splits JS arguments at any comma. This was a missed use case for having a comma in the name, and has been resolved by adding encoding for the comma value in pzMultiSeriesData FusionCharts XML rule. Then this will be decoded in the drilldown JS APIs pzPega_chart_legacydrilldown and pega_report_summary.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us