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-A3712 · Issue 222263

Removed collapse from advanced filter options to improve accessibility

Resolved in Pega Version 7.2

The advanced options in the report viewer's filter conditions were not accessible using the keyboard and would only expand with a mouse. To resolve this, the advance options collapse has been removed from PZFILTERADVANCEDOPTIONS and the information now fully displayed.

SR-A3712 · Issue 218750

Removed collapse from advanced filter options to improve accessibility

Resolved in Pega Version 7.2

The advanced options in the report viewer's filter conditions were not accessible using the keyboard and would only expand with a mouse. To resolve this, the advance options collapse has been removed from PZFILTERADVANCEDOPTIONS and the information now fully displayed.

SR-A8488 · Issue 219112

HTML line breaks honored in Excel export

Resolved in Pega Version 7.2

In Report Definition, Export to Excel was ignoring the new line of each cell due to pzDisplayPropValue not acting on the HTML tag
. To correct this, the call to the function "pzDisplayPropValue" has been modified to pass a flag which will be set based on option given on the RD rule form, i.e. "Ignore formatting when Exporting to Excel". In addition, the
tag is now supported so Excel will format it accordingly.

SR-A8488 · Issue 220333

HTML line breaks honored in Excel export

Resolved in Pega Version 7.2

In Report Definition, Export to Excel was ignoring the new line of each cell due to pzDisplayPropValue not acting on the HTML tag
. To correct this, the call to the function "pzDisplayPropValue" has been modified to pass a flag which will be set based on option given on the RD rule form, i.e. "Ignore formatting when Exporting to Excel". In addition, the
tag is now supported so Excel will format it accordingly.

SR-A9731 · Issue 222614

Pick a Value window resized for proper display

Resolved in Pega Version 7.2

On clicking on the criteria field of any report (listview / SummaryView), the 'Pick Values' modal window opens up for user to select values. This window is sized smaller by a percentage than the ClientHeight to ensure the popup can display the content within the height of the current window. After upgrade, the modals appeared with a default height of 96% and caused the Apply / Cancel / Submit buttons to either be partially visible or not visible at all, which did not allow user to select values. This has been resolved by updating the "launchpickavalue" method defined in "Rule-Obj-HTML.Wizard_Parameters" rule to set the iframe height to 93%.

SR-A12341 · Issue 224036

Corrected implementation for DataFlow key non-match

Resolved in Pega Version 7.2

If a DataFlow Dataset configured against a Report Definition had a property key name that was not identical to the column name in the database table, the Dataflow failed to execute with error " Incorrect implementation for Report Definition as a data flow source. Property-to-database table column mapping was not applied correctly". The implementation has been fixed to resolve this issue.

SR-D69098 · Issue 534042

Export to Excel works for for report definition with duplicate columns

Resolved in Pega Version 8.5

After adding a date column to a report definition (2nd column in the report), the data displayed correctly in the UI but Export to Excel failed with the error "Section 'pzRDExportWrapper' execution error on page '' of class 'Rule-Obj-Report-Definition'. : The Reference .pyDateValue(2) is not valid." This was traced to an out of bounds exception thrown if there were two or more columns with the same calculation. When preparing for export, the column with the duplicate calculation would not get added to the map of report UI fields. To resolve this, the system has been updated to allow report definition columns with the same calculation to be properly mapped to a UI field.

SR-D69108 · Issue 543846

Handling added for drag-and-drop with deleted report templates

Resolved in Pega Version 8.5

After adding a new report, an error appeared when trying to use drag-and-drop to add a column (Page List) from the Data Explorer in the report browser. This was traced to refactor work done to use the Record API throughout reporting: the ruleset on new reports was not being reset from a Pega- ruleset to an application ruleset, causing columns the referenced properties defined outside the platform to be rejected. This use case was missed because case types define their own report templates on creation, but in this scenario those had been deleted. To resolve this, the system has been updated to call pxChooseBestRuleset from pxShowReport in order to enable the use of properties defined in the application prior to saving the report.

SR-D91038 · Issue 553165

Corrected report with combo chart in Case Manager portal

Resolved in Pega Version 8.5

After adding the required columns a report in the report viewer and then adding a combo chart and dropping the summarized column on the y-axes and group by column on X-axis, clicking on "done editing" generated the error "pyUI.pyChart: You must have at least two Aggregate Columns in the chart series .pyUI.pyChart.pyDataAxis(1).pyChartOutputType: A Combo chart requires at least 1 Chart Type be a Column". Investigation showed that the second DataAxis page was getting deleted in the pzCleanChartDataAxis activity, causing the validation to fail. This has been resolved by adding a 'when' rule to "pzChartIsSingleY" that checks for "SingleYAxisClustered" chart and refers the same in pzCleanChartDataAxis to skip the data axis deletion.

SR-D90232 · Issue 555781

Combo charts now support conditional colors

Resolved in Pega Version 8.5

An enhancement has been added to facilitate the use of conditional colors in combination charts.

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