SR-C1738 · Issue 345628
Timestamp fixed for Export to Excel
Resolved in Pega Version 7.4
When trying to do a Export to Excel on a report definition with one of the columns being a Date time property, an extra 'a' was seen in the date time columns in Excel. In this case, 'a' is valid for formatting Java datetimes while 'AM/PM' is the equivalent for Excel, so the 'a' will be replaced with AM/PM in the summary viewexcel data.
SR-C2850 · Issue 348798
Missing buttons returned to Marketing report browser
Resolved in Pega Version 7.4
After upgrade, the Report Browser in the Pega Marketing portal was missing the 'Add Category' and 'Add Report' buttons. This was due to a difference in the UI-kit for the header, and has been fixed.
SR-C2920 · Issue 344845
Summary report count fixed when using filter prompt
Resolved in Pega Version 7.4
The summary data count was not getting updated in a report unless the "Prompt for filter changes before displaying report" option on Report Viewer tab (Actions -> Refresh) was unchecked. This was an error in the refresh code related to the display prompt filter check and has been corrected.
SR-C9779 · Issue 351372
Performance improvement for data page sourced by RD
Resolved in Pega Version 7.4
Performance improvements have been made to using a Data page sourced by a report definition by removing the step that creates an unneeded parameter page.
INC-147844 · Issue 612899
Check added for type of value in scheduling adaptive reports
Resolved in Pega Version 8.5.3
When scheduling the pyAdaptiveModelsOverview, pyAdaptiveModelsPredictorOverview and pyModelsActivePredictorsOverview reports, the error "atest.Snapshot_Time is not a valid date/time value" was occuring in step 1 of the pzRDExportWrapper activity. The reports worked as expected when run standalone; the failure only occurred when running from scheduled tasks. Investigation showed that the system was trying to parse a property reference as a datetime, and the failure and error caused the report scheduler to refuse to send the generated report. This has been resolved by adding logic to ReportFilter.java to check if the value is a property reference before attempting to parse it as a datetime value.
INC-149143 · Issue 613143
Report category error messages made accessible
Resolved in Pega Version 8.5.3
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 613916
Corrected page counts for 'save-as' reports
Resolved in Pega Version 8.5.3
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 615016
Cross-Site Scripting update
Resolved in Pega Version 8.5.3
Cross-Site Scripting filtering has been added to Shortcut Handle.
INC-151185 · Issue 618730
OptimizeForLargeResults flag set in BasicListSpecification to avoid OOM
Resolved in Pega Version 8.5.3
As soon as dedicated indexing started for a data type, the JVM heap occupation went beyond 99 and eventually caused a system crash due to an out of memory error. This was traced to the use of the BasicListSpecification API for retrieving results from the database always having the autocommit mode on, which loaded all instances for indexing into memory and interfered with PostgreSQL's cursors (query encapsulation). This has been resolved by adding an OptimizeForLargeResults flag that will be set to on in the BasicListSpecification activity before fetching the keys from the database.
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.