SR-A76558 · Issue 253570
Date/time data fixed for sub-report filter
Resolved in Pega Version 7.2.2
It was not possible to select filter value for the sub report date column value in main report filter condition due to the sub report date time column value not being populated correctly. This has been fixed.
SR-A24877 · Issue 250548
Widget title localization corrected
Resolved in Pega Version 7.2.2
Sporadic issues were seen with proper localization for the label of items inside any widget of the widget library. A step has been added to explicitly set the pyDescription fix this.
SR-A76162 · Issue 251024
Widget title localization corrected
Resolved in Pega Version 7.2.2
Sporadic issues were seen with proper localization for the label of items inside any widget of the widget library. A step has been added to explicitly set the pyDescription fix this.
SR-A67716 · Issue 251384
Updated ruleset determination for saving copied reports
Resolved in Pega Version 7.2.2
When a new report was made from a copy, it was not properly assigned to the ruleset it should be saved in (the "design time" ruleset configured on the operators Access Group). Instead, it was residing in the same ruleset as the template report definitions (Pega-Reporting), causing property validations to fail if they were in the subset of rulesets which were in the design time ruleset's stack but not in Pega-Reporting until the report was saved successfully once. This has been fixed by adding a step to Rule-Obj-Report-Definition!pxShowReport that sets the ruleset name and version of a new report to match the Access Group's configured design time ruleset.
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.