Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Export to PDF issues for Report Definition

SA-38698

Summary



Application got upgraded from Pega 7.1.7 to Pega 7.2.2. On exporting a report to PDF, the column headers are not visible(appear in white). Also, the grid loses all formatting. This use case works fine in Pega 7.1.7.

Error Messages



Not Applicable

Steps to Reproduce

1. Launch Case manager portal
2. Run any out of the box(OOTB) report (say "List of processes entered by operator")
3. Export to PDF
Actual behaviour: The generated PDF is different from the one in Pega 7.1.7.

Root Cause



1. When Export to PDF for the reports triggered from the designer studio, pzDesignerStudio is being picked and since pzDesignerStudio skin has given with new css features(like font-size: inherit, color: inherit etc), which were not supported by the PD4ML library and causing PDF to render in white color.
2. When Export to PDF for the reports triggered from the end user portal, pyEndUser is being picked up. Issues will not be observed, if end user skin is not using advanced css features.

In order to avoid unavoidable parsing errors with PD4ML, when ever export to pdf is triggered via designer studio or portal, pyReport_ExportToPdfStyles will be loaded and also skin file automatically removed.

Since the pyReport_ExportToPdfStyles available rule, new styles can be added for new look of the report.

Resolution

Apply HFix-34638.

Published July 27, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us