SR-A21741 · Issue 250251
Filtering and drill down fixed for encrypted values
Resolved in Pega Version 7.2.2
When one of the fields on a drill down report was encrypted, filtering would show the encrypted value but the drill down would not. This was an issue with the encoding attached to the encrypted element not being handled consistently, and has now been fixed.
SR-A69740 · Issue 250228
Scheduled Reporting Review harness refresh updated
Resolved in Pega Version 7.2.2
When saving a scheduled report task, sometimes the changes were not applied correctly in the landing page. This has been resolved by updating the Pega-ScheduledTask-Reporting.Review harness so a save action will refresh a section rather than refreshing the harness twice.
SR-A20018 · Issue 250581
Drill down fixed for use with "Do not display group headings"
Resolved in Pega Version 7.2.2
When the "Do not display group headings" setting in report viewer tab was checked in a report, drilldown did not work correctly for summarized reports that do not display group headings. This was an issue with attributes not being set for the drilldown to work with aggregate columns, and has been resolved.
SR-A20018 · Issue 250155
Drill down fixed for use with "Do not display group headings"
Resolved in Pega Version 7.2.2
When the "Do not display group headings" setting in report viewer tab was checked in a report, drilldown did not work correctly for summarized reports that do not display group headings. This was an issue with attributes not being set for the drilldown to work with aggregate columns, and has been resolved.
SR-A75959 · Issue 252005
Error messages correctly clear after copying report
Resolved in Pega Version 7.2.2
When trying to perform "Copy" of a report into the same category using the report shortcut menu from case manager portal, the error "This report shortcut already exists in this category. Please select a different category" appeared. The error persisted on the screen (harness) even after clicking on "Cancel" of Modal Dialog, and after cancelling the "Copy Report Shortcut" modal in the Report Browser with an error in the modal's form, the errors reappeared at the top and bottom of the Report Browser itself. This was due to validation messages being copied from the temporary shortcut page to the primary page so that submitting the form was prevented when there were errors, but these messages should have been cleared from the primary page when cancel was clicked. This has been fixed.
SR-A24855 · Issue 253637
Fixed Export to Excel with Microsoft Internet Explorer 11
Resolved in Pega Version 7.2.2
When using Microsoft Internet Explorer 11, Export to Excel from report definition generated the sporadic error "Unable to read file." After consulting with Microsoft, the cause was traced to the browser attempting to open the file before it was downloaded, and code has been added to check for the browser and handle the download/open appropriately.
SR-A98702 · Issue 266129
Minor update to help doc for property optimization run time
Resolved in Pega Version 7.2.2
The help file for Property optimization using the Property Optimization tool has been updated with non-critical corrections to the phrasing regarding the length of time that might be required to perform background processing.
SR-A94871 · Issue 263314
Handling added for summary report paging mode changes
Resolved in Pega Version 7.2.2
After switching a summary report previously configured to use the "Next Previous" paging mode to a list report using the "List" action in the "Actions" menu, changing to a new page caused an error to be shown and no records displayed. This has been corrected by adding a step to the activity pzPostReportSummarizeConfig to reset the paging of a report when converting from a summary report to a list report.
SR-A99642 · Issue 266586
Fixed special character encoding for Report Definition
Resolved in Pega Version 7.2.2
Double encoding of the Axis label caused issues with special characters such as apostrophes in Report Definition. This has been corrected.
SR-A92190 · Issue 261317
Added support for '&' in report parameter
Resolved in Pega Version 7.2.2
If the value of a parameter to report was set to be passed as 'A & B', the parameter value was being truncated to 'A' by the time it is received by the report. This truncation has been fixed by encoding the parameters while generating the Data-click attributes.