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.
INC-132176 · Issue 588807
Cache cleared before PDF generation to ensure proper fonts
Resolved in Pega Version 8.2.8
The font File OCRAEXT.ttf added at location "/usr/local/tomcat/fonts" was not being picked when the PDF was generated via an agent execution. When the same activity was run manually, the font issue was sporadic. Investigation showed that when multiple apps use the same props directory but different fonts directories, the handling would sometimes cause one app to use another app's props file with the result of the improper fonts mapping. To resolve this, an update has been made to clear the cache before PDF generation starts to ensure the library reads the proper fonts.
INC-132176 · Issue 588809
Cache cleared before PDF generation to ensure proper fonts
Resolved in Pega Version 8.5.2
The font File OCRAEXT.ttf added at location "/usr/local/tomcat/fonts" was not being picked when the PDF was generated via an agent execution. When the same activity was run manually, the font issue was sporadic. Investigation showed that when multiple apps use the same props directory but different fonts directories, the handling would sometimes cause one app to use another app's props file with the result of the improper fonts mapping. To resolve this, an update has been made to clear the cache before PDF generation starts to ensure the library reads the proper fonts.
SR-C30554 · Issue 370552
Template switch added to Case Worker Portal for PDF generation
Resolved in Pega Version 8.1
PDF generation was not working in the Case Worker portal due to the template mode defaulting to always ON. Since this must be OFF when the PDF flow is present, a new 'ignoreTemplatization' parameter has been added to the HarnessUIBuilder.java class. This parameter must be passed from the flow and be combined with a call to pzSetUITemplateStatus after setting that flag.
SR-C34235 · Issue 392563
Clarifications added for PDF rendering when using default values
Resolved in Pega Version 8.2
A visibility condition has been added in pzGeneralTab_ControlProps to hide the default value when .pyEditOptions value is "Read-only-always". In addition, the documentation has been updated to reflect that when default value is configured, it will be applicable only if the control renders in editable mode. If the control is editable and the property value is empty on the clipboard, the default value will be set on clipboard.
SR-D35955 · Issue 525239
Special character removed from filename of RTE uploaded into PDF
Resolved in Pega Version 8.4
An Image uploaded from RTE was not displayed in PDF if the image name had special characters. This has been resolved by setting the system to remove '%' from file names uploaded into RTE.
INC-132176 · Issue 588810
Cache cleared before PDF generation to ensure proper fonts
Resolved in Pega Version 8.6
The font File OCRAEXT.ttf added at location "/usr/local/tomcat/fonts" was not being picked when the PDF was generated via an agent execution. When the same activity was run manually, the font issue was sporadic. Investigation showed that when multiple apps use the same props directory but different fonts directories, the handling would sometimes cause one app to use another app's props file with the result of the improper fonts mapping. To resolve this, an update has been made to clear the cache before PDF generation starts to ensure the library reads the proper fonts.
SR-D75421 · Issue 552438
Parameters added to protect font size in HTML to PDF conversion
Resolved in Pega Version 8.4.2
Pega uses the pd4ml external library for HTML to PDF conversion. As part of this, the adjustHTMLWidth API was called to avoid truncation issues, but this resulted in font-sizes not being preserved in the exported document but rather changed as necessary to fit in the PDF. In order to support preserving the font size during export, the pyPDFSettings datatransform will call the protectPhysicalDimensions API along with setHTMLWidth, and avoid calling adjustHTMLWidth. With this change in place, any content width should not be set explicitly to some value as it may lead to truncation if the space is not sufficient. If there is no width set, text will wrap automatically. In case of tables with large number of columns, truncation issues may be seen: to avoid such issues, pass a larger htmlWidth value so that table will be reduced in size and in the rest of the page, font-sizes are preserved.
SR-D75421 · Issue 552435
Parameters added to protect font size in HTML to PDF conversion
Resolved in Pega Version 8.3.3
Pega uses the pd4ml external library for HTML to PDF conversion. As part of this, the adjustHTMLWidth API was called to avoid truncation issues, but this resulted in font-sizes not being preserved in the exported document but rather changed as necessary to fit in the PDF. In order to support preserving the font size during export, the pyPDFSettings datatransform will call the protectPhysicalDimensions API along with setHTMLWidth, and avoid calling adjustHTMLWidth. With this change in place, any content width should not be set explicitly to some value as it may lead to truncation if the space is not sufficient. If there is no width set, text will wrap automatically. In case of tables with large number of columns, truncation issues may be seen: to avoid such issues, pass a larger htmlWidth value so that table will be reduced in size and in the rest of the page, font-sizes are preserved.
SR-D75421 · Issue 552436
Parameters added to protect font size in HTML to PDF conversion
Resolved in Pega Version 8.2.7
Pega uses the pd4ml external library for HTML to PDF conversion. As part of this, the adjustHTMLWidth API was called to avoid truncation issues, but this resulted in font-sizes not being preserved in the exported document but rather changed as necessary to fit in the PDF. In order to support preserving the font size during export, the pyPDFSettings datatransform will call the protectPhysicalDimensions API along with setHTMLWidth, and avoid calling adjustHTMLWidth. With this change in place, any content width should not be set explicitly to some value as it may lead to truncation if the space is not sufficient. If there is no width set, text will wrap automatically. In case of tables with large number of columns, truncation issues may be seen: to avoid such issues, pass a larger htmlWidth value so that table will be reduced in size and in the rest of the page, font-sizes are preserved.