SR-D33135 · Issue 502274
Handling added for newline in a cell exported to Excel
Resolved in Pega Version 8.2.4
It was reported that new lines (br) were not displayed in exported Excel even after adding the control format with style tag <br style="mso-data-placement:same-cell;" />. This was due to a missed use case when Export to Excel was revised; as a necessity, the new Export to Excel does not support HTML as the old one did, and handling for line breaks in a cell was missed in this implementation. To correct this, wrapping has been enabled on AutoGenReportUIField and NonAutoGenReportUIField and ReportUIUtils.stripHtmlFromValue() has been updated to convert tags to line breaks.
SR-D33832 · Issue 503957
Configurability added to SLA Timeliness to allow either 0 or NULL for Unqualified records
Resolved in Pega Version 8.2.4
When using a Report Definition where the count (aggregate function) was used for both the WithinSLA and Past Deadline columns, the correct value was not getting displayed. The correct value was displayed when the sum function was used instead of the count function, but clicking 'value' returned all values despite what value was displayed on the screen. This was a behavior change related to performing a drill down action on a report definition. As per the older behavior, drill down relies on a specific value (NULL) to determine whether a record is a candidate to be shown in the drill down report. From 7.2.1 forward, drilldown relies on value 0 instead of NULL to make the average summarize function work properly, which led to a change in behavior when used with other summarize functions like sum and count. To resolve this, SLA Timeliness related RAFs have been modified to conditionally return either 0 or NULL for Unqualified records based on a DASS config.
SR-D36372 · Issue 504746
Force order added to inner join when running a Rules Resolution filter
Resolved in Pega Version 8.2.4
After upgrade, D_getResolvedWorkStatuses was not loading properly due to a Report Definition that used a Filter by Rule Resolution option timing out on the SQL Server. When the Filter by Rule Resolution option is selected in RD, it will generate a rule resolution query with an inner join which can cause a time out on the SQL Server while it tries to find out the join order for tables with multiple joins. To resolve this, the SQL server will provide a Force order, merge inner join hint option by way of an added DSS reporting/useForceOrderHint. Additionally, reporting/useMergeHintForRRquery should be set on Pega-Reporting to set things up for using the Merge Inner join hint in the query.
SR-D37943 · Issue 505735
Corrected Export to Excel after adding custom DateTime field
Resolved in Pega Version 8.2.4
An issue with exporting report definition results to Excel after adding a custom date field column through the edit report option of the report in report viewer was traced to the processing of the controls backing a cell in a report when exporting to Excel. For controls like "Date Only" DateTime (non-autogenerated) control, the code was not returning a string the way it should. To resolve this, NonAutoReportUIField has been updated to always treat all Non-auto Controls as strings.