INC-151568 · Issue 610222
Handling added for comma value in FusionCharts XML
Resolved in Pega Version 8.5.3
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-152108 · Issue 622372
Logic updated for exporting customized multi-column report definition
Resolved in Pega Version 8.5.3
While attempting to perform an export to Excel for the results of a report definition which had two custom functions for two columns, the error "PRRuntimeException: Section 'pzRDExportWrapper' execution error on page '' of class 'Rule-Obj-Report-Definition'. : The Reference .pyTextValue(2) is not valid. " was logged. The export worked if either one of the columns was removed or if "Display values across columns" in the column settings was unchecked. This has been resolved by updating the logic in PivotTableDataGridGenerator for rowheaders to handle using DisplayValuesacrossColumns with FunctionAliases when not checked on in sequence.
INC-152800 · Issue 611750
Reports filtering made accessible
Resolved in Pega Version 8.5.3
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 620244
Added accessibility to Report view context menu
Resolved in Pega Version 8.5.3
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-157974 · Issue 621965
Summary Report collapsible sections made accessible
Resolved in Pega Version 8.5.3
In order to improve accessibility, the rules 'RRDataSummaryGeneration' and 'pzDisplayGroupNodeVertical' have been updated so the clickable expand icons in summary reports will append the value of the current group when setting the text "Click to expand or collapse". This will allow JAWS to uniquely identify exactly what will be expanded or collapsed.
INC-158874 · Issue 625385
Zero value parameter handling added to Trend Reporting
Resolved in Pega Version 8.5.3
After converting the Summary Views to a Report Definition, the Chart reporting functionality was not working in the Report Definition drill-down reports; whole records present were being fetched instead of only the graph chart count. Investigation showed that one of the parameters in the FilterBy was missing, and that pxSLAAgeTimeliness used 0 instead of null, causing the system to consider all records. This has been resolved by modifying the pega_report_Summary.js file and the pxSLAAgeTimeliness FunctionAlias to handle the 0 value and ensure all parameters are present.
INC-159399 · Issue 626768
Report styles color contrast enhanced for accessibility
Resolved in Pega Version 8.5.3
In order to improve accessibility, pzReportBrowserStyles has been updated to change the report creation info color to #00000 to enhance the contrast.
INC-160825 · Issue 629370
Search landing page performance improved
Resolved in Pega Version 8.5.3
Performance improvements have been made for the Pega Platform search landing page by implementing timeouts for all requests to ElasticSearch when executing PegaIndexAdminImpl.getIndicesInfo() and changing all requests for single index to requests for all indexes. In addition, SearchUtils.areDummyDocumentsPresent() has been modified to get all 'dummy documents' in case there are duplicate dummy documents in the ElasticSearch indexes.
INC-185824 · Issue 676628
Corrected filtered column list sorting in Report Browser
Resolved in Pega Version 8.8
Sorting was not working in Report Browser for a column list when a filter category was selected. This has been resolved by modifying the pzReportListSort activity to set the correct parameters in step-1 and setting pzSetCategoryParam to retain the sortTitle parameter in step 1 with an added step -2 to call the pzReportListSort activity.
INC-198725 · Issue 707483
Elasticsearch will split queries to avoid URL length limits
Resolved in Pega Version 8.8
Elastic Search Functionality was not working and showed the status as Offline. Investigation showed that when an external Elasticsearch setup had an index prefix length = 200 and a large number of dedicated indexes, the error "too_long_frame_exception, reason: An HTTP line is larger than 4096 bytes" was generated. In this case, the system was working with approximately 87 dedicated indexes and the name for each of them was sent over the URL, resulting in this error message. This has been resolved by updating the system to split queries so as to not exceed the HTTP line limit in Elasticsearch.