SR-D48173 · Issue 515340
Resolved hang caused by cancelling report calculation
Resolved in Pega Version 8.4
When dragging a calculation into the report editor filter area, clicking X on the cancel modal that appeared caused a JavaScript exception to occur. This exception later prevented the ability to click the "done editing" button on the report. This has been resolved by modifying the pzpega_report_rafpopup.sj -- doRefresh API to pass the correct argument to reload the section API.
SR-D48442 · Issue 514047
ExportMode parameter sent to resolve duplicate rows in Export to Excel
Resolved in Pega Version 8.4
On performing Export to Excel for a report definition, duplicate rows were being exported for a column which had a TextAreaWithExpandSmall UI Control. Investigation showed that this control was looking for the exportmode parameter, which was not being sent. This parameter is now being sent.
SR-D49202 · Issue 512723
Report Definition filter editing shows all values correctly
Resolved in Pega Version 8.4
After launching a report, certain values were not populated on the pop-up when editing the filters or the commas separating the values did not appear. This was traced to the activity pzGetSelectedValues containing an older implementation of column type checking, causing it to report some embedded property references as being of type "Included Page" instead of the type of the ultimate property. This has been resolved by updating step 1 to only use this logic if pyDataType is not set, which should already be set for all filters and columns, and the formatting has been corrected.
SR-D49491 · Issue 515320
Updated sorting parameters order for better matching
Resolved in Pega Version 8.4
After choosing sorting for a column in a main summary report and then drilling down, a message appears indicating no records found even though there were results. The query showeds that the values for the 'where' clause were sent in the wrong order, causing a parameter mismatch. This has been resolved with an update to get the iterator before sorting so parameters match up correctly.
SR-D49667 · Issue 516473
Filtered By Label read by JAWS in report browser
Resolved in Pega Version 8.4
When using Firefox, any FilteredBy text in the Report Browser was not being read by JAWS. This was traced to Firefox interpreting the filters in the Report Viewer as not having any distinguishing accessibility label, and has been resolved by adding aria roles to the filters in the Report Viewer.
SR-D50569 · Issue 515437
Primary page paramter explictly set to resolve fix/edit Scheduled Tasks issue
Resolved in Pega Version 8.4
After upgrade, the top section of report details was getting blanked out when using the Reporting | Components | Scheduled Task to open a report and "update" it to fix issues. This was an unintended side effect of updating the Review harness to display the Perform harness when clicking Update, which was done to correct an earlier issue with UI validations when using the out of the box schedule report functionality. To resolve this, pxScheduleTaskWrapper has been updated to explicitly set the parameter page according to the primary page's values when not in the report browser.
SR-D50787 · Issue 520485
Excel time values will default to server datetime if operator time zone is null
Resolved in Pega Version 8.4
After upgrade, a scheduled report that contained a column using pxDateTime that was supposed to use EST instead used GMT when run and exported to Excel. This has been resolved with an update that will default to using the time zone of the server If the time zone of the operator is empty or null.
SR-D50819 · Issue 519238
Eligibility Builder integer sorting revised
Resolved in Pega Version 8.4
In 'Offer' on the Eligibility tab, the Builder was sorting integer properties by the value of the integer as a text string rather than the whole number. Example: 1, 10, 12, 13, 100, 2, 20, 29, 299, 3 instead of the expected 1, 2, 3, 10, 11, 12, 20, etc. This was traced to the system sorting the results using tools.sortPageList() in order to sort by localized (string) value, which is not appropriate for values of any type other than string. To resolve this, the system will skip the manual sort step for numeric columns since the values are appropriately sorted by the database.
SR-D55289 · Issue 524108
FusionCharts upgraded to resolve drill down issues
Resolved in Pega Version 8.4
Drill down reports were not working when the results were displayed with huge data that came up with a scroll bar or if the report was scrolled down and a drill down was attempted when the scroll bar was in the bottom or middle of the scroll line. The hover icon was different i.e., the hand icon was replaced with arrow icon, or sometimes the hand icon displayed without showing the data. The tooltip was also not displaying as expected when hovering on the chart. It was possible to drill down when the scroll bar was in the top or the focus was moved outside the chart and brought back in again. This was traced to bugs in the FusionChart libraries, and has been resolved by upgrading to FusionCharts 3.14.0-sr.1.
SR-D55801 · Issue 524293
Corrected HTML error generated on export to PDF
Resolved in Pega Version 8.4
After exporting a report to PDF, the PDF could be viewed but repeated instances of the error "<th> missing ‘>’ for end of tag" were logged. This was traced to missing the closing '>' for th in the pzRRDataListHeaderRow HTML rule when "Enable column command menu" is unchecked in ReportViewer options, and has been corrected.