INC-127723 · Issue 569493
Ad hoc reports saved successfully in private categories
Resolved in Pega Version 8.4.2
After upgrade, an error was seen when attempting to save an ad hoc report in a private category. Saving in a public category worked as expected. This was traced to the Rule-Shortcut.Validate activity, which attempted to use the Rule-Shortcut's RuleSet to find the Rule-Category. To resolve the saving issue, the Rule-Shortcut.Validate activity has been updated to do an Obj-Open on the Category instead.
INC-128881 · Issue 566522
Added check for UIInspector privilege to Pega-ScheduledTask-Reporting class
Resolved in Pega Version 8.4.2
The pyEnableUIInspector 'when' rule in the Pega-ScheduledTask-Reporting class was not evaluating the presence of pxUIInspector privilege, causing the live UI icon to be visible to users who were not intended to see it in the interaction portal while scheduling reports. This was traced to an error in the related Rule for the 'when', and has been resolved by adding an evaluation of the the presence of pxUIInspector privilege to the pyEnableUIInspector 'when' rule in the Pega-ScheduledTask-Reporting class.
SR-D88419 · Issue 557945
Corrected date formatting for use as a custom filter
Resolved in Pega Version 8.4.2
Given a Report Definition with custom filter section, when the custom filter section had a date property which was used under filters, the filter was not shown as a date. The date was shown properly when the custom filter section was not used. This was related to the date conversion for the locale, and has been resolved by modifying the RRFilters_Logic to remove a check for dates ending in GMT and replace it with a check whether the report uses a custom filter section. This runs the correct logic to render the date as expected.
SR-D88500 · Issue 562657
Eligibility prompt integer values sorted by incremental size
Resolved in Pega Version 8.4.2
In an Offer rule on the Eligibility tab of the Eligibility Builder, an eligibility row using {integer property} comparator {value} had the list of prompt values sorted alphabetically for integer values rather than incremental size when using Select value -> Existing Values. This has been corrected by revising the logic in addValuesToOutputPage to call Report.sort with different sorting algorithm for numeric values. Logic was also updated to call Report.sort for prompt lists.
SR-D89071 · Issue 569733
Case status label localized in export to Excel
Resolved in Pega Version 8.4.2
The Case status(.pyStatusWork) value was not localized in export to Excel. Investigation traced this to Report definitions not passing default parameters specified on the property ruleform for the "default control". Therefore, the first 'when' condition in WorkStatus was evaluating as false, which caused the wrong field value to be used for reports. To resolve this, the first 'when' condition of WorkStatus control has been updated to succeed if the useStatusWorkFieldValue parameter is not passed. The default is true when it is not present.
SR-D90232 · Issue 555782
Combo charts now support conditional colors
Resolved in Pega Version 8.4.2
An enhancement has been added to facilitate the use of conditional colors in combination charts.
SR-D91038 · Issue 553166
Corrected report with combo chart in Case Manager portal
Resolved in Pega Version 8.4.2
After adding the required columns a report in the report viewer and then adding a combo chart and dropping the summarized column on the y-axes and group by column on X-axis, clicking on "done editing" generated the error "pyUI.pyChart: You must have at least two Aggregate Columns in the chart series .pyUI.pyChart.pyDataAxis(1).pyChartOutputType: A Combo chart requires at least 1 Chart Type be a Column". Investigation showed that the second DataAxis page was getting deleted in the pzCleanChartDataAxis activity, causing the validation to fail. This has been resolved by adding a 'when' rule to "pzChartIsSingleY" that checks for "SingleYAxisClustered" chart and refers the same in pzCleanChartDataAxis to skip the data axis deletion.
SR-D97193 · Issue 556552
DataView rules and library files removed
Resolved in Pega Version 8.4.2
After upgrade, the pzPresentationFUA library was failing while compiling with errors relating to references for com.pega.pegarules.priv.desktop.reporting.dataview not being resolved. This was due to an incomplete cleanup when data views were removed from use, and the library and rules have now been removed.
INC-120343 · Issue 573077
Explicit parent added for descendants in subreport to correct summary
Resolved in Pega Version 8.4.2
When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.
INC-85195 · Issue 567389
Search timeout made more consistent
Resolved in Pega Version 8.4.2
Perform a global search was not honoring a time out set to 5 seconds. This was due to inconsistent application of enforcing the timeout because the values were kept in different ways for different functions. To resolve this, timeout keeping for searching has been reworked and made more consistent so that searching will use a custom timeout if it is contained in the report definition and will otherwise fall back to using the appropriate DSS settings for Embedded Elasticsearch, External Elasticsearch, and Search & Reporting Service.