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.
SR-D58552 · Issue 522088
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-D65937 · Issue 528980
Support added for calling Export to Excel directly from RD
Resolved in Pega Version 8.4
When using Export to Excel directly from a report definition, a date column specified using pxDatetime was shown as applied date format in the resulting Excel file. The column was formatted as expected if the export was called from an activity. This was traced to the recent refactoring of Export to Excel: it was not expected that it would be called directly, but rather that it would be invoked from a report viewer ruleform. In order to support this direct use, step calls have been added to the pzRDExportWrapper activity to call pzMergeAutoGen before the engine call. This step will merge the pyModes pages from pxDateTime control.
INC-127102 · Issue 602697
Synchronized BatchStatus email available for multi-node
Resolved in Pega Version 8.6
An enhancement has been added which will handle synchronization between BatchStatus used in different events on different nodes and send email notifications.
INC-128880 · Issue 592816
Handling added for angle brackets in legacy Chart control
Resolved in Pega Version 8.6
When using Investigative Case Management, some report charts were not rendering correctly. This has been resolved by updating appendFormattedString in AbstractJsonDataGenerator.java to escape angled brackets (< and >) before appending the input.
INC-132169 · Issue 584760
NativeSQL will use inline rule resolution for core components
Resolved in Pega Version 8.6
After upgrade, nodes were going down with a heartbeat error. This was traced to issues with NativeSQL taking a very long time to generate queries due to the overhead in calling multiple complex functions to resolve rules. To correct this, updates have been made to resolve the standard set of functions used by core components inline in NativeSQL function resolution.
INC-133482 · Issue 605003
Corrected isExternal flag not resetting
Resolved in Pega Version 8.6
Corrected isExternal flag not resettingIf an extraction referred to external tables, an isExternal flag that was set to true during the Extraction process did not get reset to false for the tables which were not referring to external. This has been corrected.