SR-A21931 · Issue 233188
XY chart Dashboard reports updated to handle empty data
Resolved in Pega Version 7.2.1
Dashboard reports were not loading when using RD as the source for XY charts if the data returned was completely empty. RUF: pzControl ? pzRuntimeFusionXYDataJSON has been updated to handle this missing use case.
SR-A22365 · Issue 243530
Multi-parameter function value handling added to Report Definition chart
Resolved in Pega Version 7.2.1
When a chart control was configured using the property panel in design view, the chart preview did not update appropriately if it used a column defined by a function that with two or more parameters. To handle this, part of com.pega.pegarules.priv.desktop.reporting.chart.AutoChartConfigTranslator.translateDataItem(DataItem, ClipboardPage) has been refactored such that it only splits pyReportColumnKey on the first ',' (comma).
SR-A22993 · Issue 247098
Date format and alignment updated for Export to Excel
Resolved in Pega Version 7.2.1
When using Report Definition for a case search with the out-of-the-box excel export, formatting one of the DateTime type properties to display only the date portion in the exported report was not working as expected in the repeated-grid while it did work properly in report definition export function. The problem existed in the generation for the Report Definition itself due to the control formatting the data to be mm/dd/yyyy without the days even though the data type is a datetime, and the function has been updated to pass "date" as the datatype when a datetime is being formatted as a date.
SR-A23457 · Issue 245079
Tab
Resolved in Pega Version 7.2.1
In a tabbed layout, opening a modal window resulted in the tab name being changed to that of any active window. This was an error in the drilldown window logic, and has been corrected.
SR-A23665 · Issue 248776
Percentage calculated by control carried into Excel export
Resolved in Pega Version 7.2.1
If a Report Definition calculated the percentage by using the control, the percentage would display in the report browser but 0.00% would be displayed in the Export to Excel. The step page for the control being executed at display time and export are different, so the activity is unable to get the ".pySummaryCount(1)" from the step page. To fix this, pzGetHTMLPropertyValue has been modified so it acts on the step page of the property rather than the primary page the function was executed against.
SR-A23692 · Issue 245660
Scheduling dialogue correctly releases lock on browser pop-up exit
Resolved in Pega Version 7.2.1
Opening the scheduling dialogue for a currently scheduled report created the proper locking, but "X"-ing out of the pop-up report window without editing it was not releasing the lock and the report was then not executed as scheduled. To avoid this, a Rule-Obj-Casetype has been added to control when the schedule is locked and will also release the lock when the changes fail validation.
SR-A23709 · Issue 247989
Performance improvements for Scheduled Export to Excel
Resolved in Pega Version 7.2.1
Some memory usage improvements have been made for exporting reports to Excel through the scheduler.
SR-A23735 · Issue 248542
Image/Label of Report checkbox clickable
Resolved in Pega Version 7.2.1
In the Report Browser, icons and text labels have been linked to the checkbox and are clickable to check/uncheck the list/chart/summary filters.
SR-A23912 · Issue 246952
Custom filters won't display header container icons
Resolved in Pega Version 7.2.1
Unwanted icons were appearing when using a custom filter section that has a grid with a header/title, such as an 'X' close icon displaying next to an included section/repeat grid coupled to the filter section launched from the report browser for a report definition. The harness that displays the filter section has been modified to not include the icons that come with a container that has a header.
SR-A24516 · Issue 247668
Reports correctly deleted
Resolved in Pega Version 7.2.1
Reports are not deleted after deleting a shortcut, causing errors when trying to create reports using the same name. The logic for UpdateCheckIn has been corrected so that it will not jump to block the rule and will instead delete the rule.