SR-B56777 · Issue 312300
Vertical scrollbar refinements for report editor
Resolved in Pega Version 7.3.1
To fix a previous scrolling problem, the layout of the report editor was altered to accommodate a vertically resizing header. This involved removing the absolute positioning of the sidebar and main panel that allowed independent scrolling. This has been further refined to use flexbox to prevent wrapping in the header (on desktop only).
SR-B52348 · Issue 308690
Restored option to allow PDF export for chart actions
Resolved in Pega Version 7.3.1
Updates to the version of Fusion included in Pega caused support to be lost for "Export to PDF". This broke a 'when' rule that allowed export of a chart embedded in a section by selecting "Show data". To restore that function, the 'when' step in pyReport_ShowChartWhenShowingData that disables the chart when running the report in "dataonly" mode has been changed. The 'when' rule will default to not showing the chart for backwards compatibility, but can be overwritten to show the chart.
SR-B51933 · Issue 314418
Fixed RD shortcut for opening multiple reports in multiple tabs
Resolved in Pega Version 7.3.1
When a Report Definition was launched via Navigation -> Actions -> Run Report and Target was selected as 'New Document', multiple reports were not opening in multiple tabs side by side. Instead, when the previous report tab was closed the new one was opened. The display worked as expected when Target was selected to be 'Replace Current' or "Open in Pop-up" or if the entire browser was refreshed. The issue was traced to an incorrect calculation in a short cut handle, and has been fixed.
SR-B54906 · Issue 313350
Column calculations fixed for RD exported to Excel
Resolved in Pega Version 7.3.1
When exporting a report definition that contains calculated columns to Excel, the columns were either blank or 0% for each row even though the correct calculated values appeared in both the HTML preview and the PDF export. Additionally, date formatting was not applied in the Excel export. This was due to legacy code inserted in an earlier version of Pega to repair Export to Excel; the fix is no longer necessary since the exporting function was reworked, and has been removed.
SR-B48373 · Issue 306064
App Explorer enhanced to support expanded number of built-ons
Resolved in Pega Version 7.3.1
When the number of built on applications was more than 50, Application Explorer did not display all the results. This was a legacy issue: at the time the report definition code was developed there was no support for multiple built-on applications. The max records for the query for validating the application chain was not configured, resulting in a default value of 50. In order to support more complex use, pyMaxRecords is now set to 0.
SR-B49305 · Issue 307379
XSS filtering added to Chart Title
Resolved in Pega Version 7.3.1
XSS security filtering has been added to the Chart Title in the Chart Editor.
SR-B52024 · Issue 308435
XSS filtering added to Chart Title
Resolved in Pega Version 7.3.1
XSS security filtering has been added to the Chart Title in the Chart Editor.
SR-B44352 · Issue 306061
Fixed exported PDFs of scheduled email reports in DS
Resolved in Pega Version 7.3.1
Scheduled email reports that were converted to PDF were not readable, appearing as a list of rules in a very small font in white over a very light grey. This happened when the "export to pdf" command came from the designer studio; pzDesignerStudio was being picked and using a skin with new CSS features like font-size: inherit, color: inherit etc., which were not supported by the PD4ML library. As a workaround, it was possible to ignore the skin while exporting the PDF via enabling the "Ignore application skin when exporting to PDF" data access tab of the report, causing the system to consider the styles from the pyReport_ExportToPdfStyles available rule instead of skin. As a permanent fix, the system will avoid encountering parsing errors with PD4ML by loading "pyReport_ExportToPdfStyles" and automatically removing the skin file whenever export to PDF via designer studio is triggered.
SR-B48598 · Issue 305742
Fixed exported PDFs of scheduled email reports in DS
Resolved in Pega Version 7.3.1
Scheduled email reports that were converted to PDF were not readable, appearing as a list of rules in a very small font in white over a very light grey. This happened when the "export to pdf" command came from the designer studio; pzDesignerStudio was being picked and using a skin with new CSS features like font-size: inherit, color: inherit etc., which were not supported by the PD4ML library. As a workaround, it was possible to ignore the skin while exporting the PDF via enabling the "Ignore application skin when exporting to PDF" data access tab of the report, causing the system to consider the styles from the pyReport_ExportToPdfStyles available rule instead of skin. As a permanent fix, the system will avoid encountering parsing errors with PD4ML by loading "pyReport_ExportToPdfStyles" and automatically removing the skin file whenever export to PDF via designer studio is triggered.
SR-B66139 · Issue 316025
Localization fixed for report name place holders
Resolved in Pega Version 7.3.1
The Report Category Name Place holder was not being localized if it contained special characters. Handling has been added to correct this.