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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C19348 · Issue 359143

Editable PDF creation added

Resolved in Pega Version 8.1

A new feature has been added to allow creation of an editable PDF via an added flag in the activity HtmltoPDF.

INC-216404 · Issue 721512

Table alignment corrected for PDF

Resolved in Pega Version 8.6.5

The align="center" styling was not getting applied whenever the Rich Text Editor was in readonly mode. To resolve this, the CSS style has been updated to correct table center alignment for readonly Rich Text Editor documents and paragraphs in the pzbase-gadgets-ckeditor and pzbase-div-layout CSS files respectively.

INC-216404 · Issue 721510

Table alignment corrected for PDF

Resolved in Pega Version 8.8

The align="center" styling was not getting applied whenever the Rich Text Editor was in readonly mode. To resolve this, the CSS style has been updated to correct table center alignment for readonly Rich Text Editor documents and paragraphs in the pzbase-gadgets-ckeditor and pzbase-div-layout CSS files respectively.

SR-A20072 · Issue 238701

Portal markup in PDF resolved

Resolved in Pega Version 7.2.1

When using the Google Chrome browser, the portal harness markup was being included in PDFs generated from the user portal due to the frameless dynamic container. This has been corrected.

SR-A20072 · Issue 240043

Portal markup in PDF resolved

Resolved in Pega Version 7.2.1

When using the Google Chrome browser, the portal harness markup was being included in PDFs generated from the user portal due to the frameless dynamic container. This has been corrected.

SR-C36337 · Issue 376557

Harness handling updated for PDF generation

Resolved in Pega Version 8.1

If a PDF was generated using HTMLtoPDF activity with a section that consists of Required input fields, the asterisk symbol for the required field was displayed as text (required) in the PDF. This was caused by the harness not being properly passed to the child for the PDF generation, and has been fixed.

SR-C93070 · Issue 431191

Fixed Export to PDF page formatting

Resolved in Pega Version 8.3

A formatting issue was seen when using export to PDF; the first page contained only the title of the report as well as the filter, the generated date, and the number of records, and the exported data was included only from the 2nd page onwards. This has been corrected, and some performance improvements for the generation time were added.

SR-C93070 · Issue 431218

Fixed Export to PDF page formatting

Resolved in Pega Version 8.3

A formatting issue was seen when using export to PDF; the first page contained only the title of the report as well as the filter, the generated date, and the number of records, and the exported data was included only from the 2nd page onwards. This has been corrected, and some performance improvements for the generation time were added.

SR-C94190 · Issue 434654

Fixed Export to PDF page formatting

Resolved in Pega Version 8.3

A formatting issue was seen when using export to PDF; the first page contained only the title of the report as well as the filter, the generated date, and the number of records, and the exported data was included only from the 2nd page onwards. This has been corrected, and some performance improvements for the generation time were added.

SR-C94190 · Issue 435433

Fixed Export to PDF page formatting

Resolved in Pega Version 8.3

A formatting issue was seen when using export to PDF; the first page contained only the title of the report as well as the filter, the generated date, and the number of records, and the exported data was included only from the 2nd page onwards. This has been corrected, and some performance improvements for the generation time were added.

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