PDF/UA support
Valid from Pega Version 8.4
PDF documents that you generate in Pega Platform™ are now in PDF/UA format. This enhancement improves accessibility for users who rely on assistive technology, such as screen readers.
For more information, see Setting PDF file versions.
Upgrade impact
With an upgrade to Pega Platform 8.4 and later, the underlying PD4ML library in Pega Platform changes from v3.10 to v4.x. Following an upgrade, most standard HTML-CSS conversions to PDF work seamlessly; however, if you use the following custom coding in their application to convert HTML to PDF, you may find that PDF generation works differently than expected or no longer works:
- Application layer Java in activities that directly link to the underlying PD4ML library
- A Rule Utility Function
- PD4ML tags in HTML fragments
For example, the following PD4ML proprietary CSS keywords are no longer supported in v4.x:
- pd4ml-page-break-border-top
- pd4ml-page-break-border-bottom
What steps are required to update the application to be compatible with this change?
After you upgrade to Pega Platform 8.4 and later and find your PDF generation works differently than expected or no longer works, you should consult the latest documentation available at pd[4]ml support site. You may also consider using the Compact CSS instead of the application skin for PDF generation; for details, see Creating PDF files by using a compact style sheet.
Personalized views in table layouts
Valid from Pega Version 8.4
Table layouts now provide users with the option to save preferred run-time configurations, such as column visibility and filtering, as permanent profiles. This enhancement helps users create dedicated views for specific work scenarios, which reduces the need for repetitive adjustments to the user interface and improves productivity.
For more information, see Enabling table personalization.
Upgrade impact
After an upgrade to 8.4 and later, the default table toolbar styling and experience may be unexpectedly different for any customized tables in a client's application: if you enabled a tool bar action for a personalizable table and the 8.4 application overrides your customization, your application now displays the default 8.4 table toolbar.
What steps are required to update the application to be compatible with this change?
Existing clients that upgrade to Pega Platform 8.4 and later may need to update applications in some scenarios. Any custom actions present in the overridden section may need to be re-authored into this toolbar using the additional actions section.