Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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.

SR-B66454 · Issue 316846

Support added for filtering labels in Join

Resolved in Pega Version 7.3.1

When class join was used in a report and the property used for filtering was a SinglePage property of the join class, then the label was not coming up in the Report Filter section. This was due to filtering labels not being shown when Join is used, and support for this has been added.

SR-B71969 · Issue 326817

Date fixed for Export to Excel

Resolved in Pega Version 7.3.1

Dates were not being formatted correctly on Export to Excel of a report definition. This was due to an error in exporting just the date field that was not previously considered when repairing the date/time function. To fix this, Export_Date_RD has been updated to export the date in a consistent manner that Excel will understand (similar to how its being done in pzExport_Datetime_RD).

SR-B73478 · Issue 325315

Chart date column duplication resolved

Resolved in Pega Version 7.3.1

Report definition charts were displaying duplicate date columns when the operator time zone was set to "Europe/London". To correct this, the system will conditionally set the time zone only when it's a datetime when normalizing the data.

SR-B73531 · Issue 325518

Missing check added for "Column Command Menu" on summary type report

Resolved in Pega Version 7.3.1

For a summary type report, the column command menu was still displayed even though the "Enable Column Command Menu" was unchecked on the report definition Report Viewer tab. This was due to a missing check for "Enable column command menu" before adding the showReportRCMenu onclick event, and has been fixed.

SR-B74586 · Issue 325692

Fixed save-as for RD with sub-report and join

Resolved in Pega Version 7.3.1

A save-as for the existing Report Definition rule :USCANSaleEstimate was not working for a new ruleset version. This was an issue with an existing RD that had a sub-report and was joined by a column in the sub-report that was a function, and pzGenerateMsgForUderDefinedFunctions has been modified to correct this.

SR-B76880 · Issue 326010

Repeat grid filtering option fixed for Microsoft Internet Explorer 11

Resolved in Pega Version 7.3.1

The repeat grid populated when running report definition was prompting for the filter of the data properly in Microsoft Internet Explorer 11, but no action was performed when clicking on it. This was an issue with missing navigation rule changes, which have been added.

INC-118918 · Issue 562155

Table Pagination elipses display properly for more than 10 pages

Resolved in Pega Version 8.4.2

When a table layout was configured with a report definition as the Data Source, the Pagination format in the grid header properly showed 'Page 1,2,3 ...' if there were fewer than 10 pages, but if there were more than 10 pages the '...' (elipses) were not appearing. This has been corrected.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us