INC-147856 · Issue 607134
Description input for new reports restricted to 64 characters
Resolved in Pega Version 8.4.4
After saving a report with a description containing more than 64 characters, trying to delete the same report generated error messages saying the report description exceeds 64 characters. There was no maximum character limit set on the description input when creating/editing/save as a report. The delete modal shows any page-level warnings, so the guard rail warnings show up at that time. This has been resolved by disallowing the creation of a description greater than 64 characters in length.
INC-149143 · Issue 613141
Report category error messages made accessible
Resolved in Pega Version 8.4.4
In order to improve accessibility while creating new reports, labels have been added to the error messages on the category name field.
INC-150193 · Issue 613914
Corrected page counts for 'save-as' reports
Resolved in Pega Version 8.4.4
The total pages count and last page icon were not displaying when the Preview button was clicked after a save-as of a report in the Report Browser. Investigation tracked this to a visible when condition on those fields that was being changed to the default of false during the save-as, and this has been resolved.
INC-151102 · Issue 615015
Cross-site scripting update
Resolved in Pega Version 8.4.4
Cross-site scripting filtering has been added to Shortcut Handle.
INC-151568 · Issue 610221
Handling added for comma value in FusionCharts XML
Resolved in Pega Version 8.4.4
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.
INC-152800 · Issue 611749
Reports filtering made accessible
Resolved in Pega Version 8.4.4
In order to ensure accessibility, titles and helper texts have been added to the text fields and checkboxes that appear in the Edit Filter non-modal window after a 'Filtered By' value is selected on the My Reports page.
INC-153692 · Issue 620243
Added accessibility to Report view context menu
Resolved in Pega Version 8.4.4
When on the My Reports screen and a Summary report is selected, the Report Viewer displays a Summarized Reports table with a column header that opens a command menu upon right-click of the mouse. This functionality is enabled in the Report Definition rule by selecting the checkbox Enable column command menu under the Report Viewer tab. Although keyboard users can open the menu via Shift+F10, keyboard users who cannot see the screen were not informed that this functionality is available as the screen reader did not announce this. This has been resolved.
INC-118918 · Issue 562155
Table Pagination elipses display properly for more than 10 pages
Resolved in Pega Version 8.4.2
When a table layout was configured with a report definition as the Data Source, the Pagination format in the grid header properly showed 'Page 1,2,3 ...' if there were fewer than 10 pages, but if there were more than 10 pages the '...' (elipses) were not appearing. This has been corrected.
INC-119669 · Issue 562589
Special character handling added to filters for table sourced with parameterized Report Definition
Resolved in Pega Version 8.4.2
Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.
INC-125641 · Issue 573386
Column Filter working with class join
Resolved in Pega Version 8.4.2
When a class join was configured in the report definition and the report was edited to include new columns from the joined class, a "Filter condition invalid" error appeared in the tracer after adding a filter condition to a new column. This was only observed when the property added was a decimal property, and did not happen for a text property. The filter worked as expected after re-saving the property in the report definition in Designer Studio. This was traced to the data type being passed as "DECIMAL" for decimal fields, which did not match the logic used to set the filter value, and has been resolved.