Anypicker control is now available
Valid from Pega Version 8.4
The new Anypicker control displays a drop-down list of values that you can group into expandable categories for faster browsing. To save time and improve search accuracy, the Anypicker control filters the available values based on the characters that the user enters.
For more information, see Adding an Anypicker control.
Default support for skip links
Valid from Pega Version 8.4
All Pega Platform™ access groups now support skip links by default. Before, you had to create special access groups for users who require skip links for screen readers. Now, the feature is automatically enabled for every group, which improves the user experience and simplifies development.
Custom activities protection
Valid from Pega Version 8.4
Unauthorized users can no longer access or use custom activities. This enhancement improves system security and makes application maintenance more intuitive.
Hierarchical table overhaul
Valid from Pega Version 8.4
The hierarchical table layout now uses a redesigned architecture that enhances stability and presentation. This update also improves accessibility by implementing ARIA guidelines and introducing keyboard navigation in tables.
For more information, see Creating a hierarchical table layout.
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.