Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

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.

Limited access for end user portals

Valid from Pega Version 7.1.1

The following portals are only accessible from supported versions of Internet Explorer in “quirks” mode:

  • WorkUser
  • WorkManager

Nesting dynamic containers not supported

Valid from Pega Version 7.1.1

Do not include a section containing a dynamic container inside of another dynamic container. This configuration may cause performance issues resulting in unexpected behavior at runtime, and is not supported.

Text Input control number type does not validate

Valid from Pega Version 7.1.5

When a Text Input control type is set to "Number" in the Presentation tab:

  • Validation does not trigger and the field is blanked out when a user submits the form.
  • If a value other than a number is entered, the browser sends an empty value, and the value is not validated.
  • In the Clipboard, the field value displays as empty.
  • If the field is required, the validation displays.

This issue occurs when using both the Chrome and Safari web browsers, and is a result of browser behavior for the HTML5 type=“number”. To fix this issue when using these browsers, do not use the "Number" type in Presentation tab of a Text Input control. Instead, the type should be set to "Text".

Unclear error message when saving shared class instance in tenant layer

Valid from Pega Version 7.1.5

If you attempt to save a shared class instance from the tenant layer, Pega 7 displays this message:

This record has x errors. Save Failed: There was a problem saving an instance of class: Error Code: <none> SQL State: <none> Message: <none>

You cannot save a shared instance from the tenant layer if that instance cannot be overridden.

Set a time zone for the DateTime control

Valid from Pega Version 8.3

The DateTime control now supports the selection of a specific time zone. Apart from the default local time zone, you can choose a Java-supported time zone or enter a property. For example, you can make it easier for a manager working in New York to schedule a task for a worker in London by configuring a calendar picker on user forms to show a date and time for Europe/London.

Beginning with this release, the calendar picker defaults to the current time in the time zone that is defined in the operator record. Previously, it defaulted to the local time zone of the system.

For more information, see Specifying a time zone for a DateTime control.

Upgrade impact

After a successful upgrade, the DateTime gadget displays the time in the current operator's locale, which is defined on the operator rule form or in the browser.  

What steps are required to update the application to be compatible with this change?

If you need to display the system time from which the user has logged in, and if this is not the same as the time in the user's locale (based on the browser setting), set the Locale field in the operator ID to be blank so that the browser-based setting and the displayed time are the same as the system time.

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