SR-B30410 · Issue 294913
Report drilldown works with 'do not display group headings'
Resolved in Pega Version 7.3
When sub-report properties were used in the main reports column source, the report definition displayed the expected results when clicking on a configured drilldown report and chart but displayed no results when listview dataset was clicked. This was traced to having "Do not display group headings" enabled in combination with drilldowns, and has been resolved.
SR-B30713 · Issue 296998
New activity pyCustomValidator added to pzValidateCustomFilterSection
Resolved in Pega Version 7.3
When a report definition enables "Prompt for filter changes before displaying report", and the report specifies a custom filter section, the harness that displays the custom filter section (pzRRDisplayCustomFilterSection) is Final and was not available to validate the fields in the custom filter section. To enable this use, a new available activity "pyCustomValidator" has been added and can be called from pzValidateCustomFilterSection.
SR-B31873 · Issue 298086
Review/Perform harness modifications for scheduled report errors
Resolved in Pega Version 7.3
Scheduled reports would periodically go to Completed state and stop running prematurely. Deleting and then reopening a scheduled report (from recents) caused corruption of scheduled reports that are re-scheduled. This was traced to the Review/Perform harness going in to a corrupt state, and has been corrected by re-building the Review harness as well as some minor changes to the Perform harness to ensure the correct buttons are displayed when deleting a scheduled report and reopening it from the recents list.
SR-B32056 · Issue 299068
CustomFusionChart display fixed for mobile HC
Resolved in Pega Version 7.3
Charts were not loading a second time unless a refresh of that section was forced after switching from one tab to other from the navigation panel on left side. This was an issue with charts created using pzCustomFusionChart erroring out when loaded within a layout group that requires the user to swipe left/right to view them in the hybrid client, and has been fixed.
SR-B33991 · Issue 292845
Corrected ability to hide filters for Export to PDF
Resolved in Pega Version 7.3
The "Display report filters" check-box was not being honored on export to PDF, causing the filters to always be shown. This has been corrected with an added visibility condition to show or hide a filter section based on the value of .pyDisplayReportHeader, and a check has been added in "RRBodyDiv" HTML rule to show header only when pyDisplayReportHeader is true.
SR-B35821 · Issue 296032
Extra space removed from "Filters: " in RD
Resolved in Pega Version 7.3
When a Report with a large number of columns was generated using Report Definition with enable add filters checked in the report definition rule, an unnecessary space appeared between the "Filters:" label and the filters. This has been removed.
SR-B37775 · Issue 300342
Action item refresh properly triggers
Resolved in Pega Version 7.3
Refresh was not clearing the temporary filters applied on the report definition results if the refresh option was triggered by the actions button. This has been fixed by adding a new java step to pzRunWrapper activity to clear the previously applied filters.
SR-B38619 · Issue 298574
Action item refresh properly triggers
Resolved in Pega Version 7.3
Refresh was not clearing the temporary filters applied on the report definition results if the refresh option was triggered by the actions button. This has been fixed by adding a new java step to pzRunWrapper activity to clear the previously applied filters.
SR-B38674 · Issue 301022
Descendant class logic made more robust
Resolved in Pega Version 7.3
The 'Report on descendant' option in the report definition/Listview was giving incorrect results. This was caused by the code used to execute the RD looking up the descendant class from the current application that inherits from the applies-to class (tools.getDatabase().getConcreteDescendantsInCurrentApplication(class name);) of the RD and executing the RD against this class. While this is appropriate when an application is built on another and case types are directly inherited into the new layer, this will not work when application layers are added which do not include equivalent case types for every case from the built upon applications. This becomes a more common problem when the MBO feature starts getting used more often on the customer implementations. To ensure the descendant class is correct, the Useimplemenation class has been updated to be more robust.
SR-B38980 · Issue 299227
createDateTimeCategories function modified to use operator time zone
Resolved in Pega Version 7.3
A report definition chart using the operator time zone of "Europe/London" and locale "en_US" displayed duplicate date columns. Updating the operator time zone to "America/New_York" removed the problem. This issue was caused by the system always parsing/formatting the date with the default local time zone, and has been resolved by modifying the parseDate/formatDate/createDateTimeCategories function to use the operator time zone instead.