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.

Updated default dynamic system setting for requestor pools

Valid from Pega Version 8.4

Clients can now enable or disable requestor pools for processing service requests using a new dynamic system setting called EnableRequestorPools with Pega-IntegrationEngine as the owning rulest. Previously, all deployments utilized requestor pools to improve service processing response efficiency; requestor pools eliminated overhead by automatically returning a requestor to the pool after it fulfills a service request. Starting in Pega Platform 8.4, requestor pools are disabled in Client-managed cloud deployments, since these deployments use autoscaling to handle service request traffic. Enabling requestor pools in Kubernetes environments is not recommended, because they can inhibit the default autoscaling settings in the environment.

Requestor pools remain enabled by default in Pega Cloud and on-premises environments.

To help clients navigate this change, Pega has updated its best practice guidance for configuring requestor pools. For an overview, see Requestor pooling for services. For guidance on the use of requestor pools in your application, see the EnableRequestorPools entry in Dynamic system settings data instances.

Upgrade impact

Requestor pools are disabled by default in Pega Platform 8.4 in client-managed cloud deployments. Clients who deployed previous versions of Pega Platform on a Kubernetes environment and who upgrade to Pega Platform 8.4 could see that their services behave differently.

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

If clients that are deployed in a Client-managed cloud environment need to configure their services to use requestor pools and they understand how to configure requestor pools for their optimized use, these clients can re-enable requestor pools. Clients should review the best practice for configuring requestor pools before they re-enable requestor pools. To re-enable requestor pools, you modify the EnableRequestorPools setting in the Pega-IntegrationEngine Owning ruleset from “disabled” to Enabled [no value]. For details, see Editing a dynamic system setting.

Improved case auditing in App Studio

Valid from Pega Version 8.5

In Cosmos UI, App Studio now supports expandable case steps. This enhancement helps users quickly navigate a case and provides deeper insight into the case flow. In addition, Cosmos UI also introduces an improved history view that helps you better meet your business auditing requirements.

For more information, see Managing Cosmos UI settings in case designer.

Upgrade impact

After an upgrade to Pega Platform 8.5 or later, the history and chevron designs change automatically. However, applications with custom history settings might still display the styling that you defined in the override.

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

If your application uses custom settings and you want to use the updated history, remove the overrides from the pyWorkCommonActions rule.

Failed Robotic Assignments work queue type changed to Standard

Valid from Pega Version 8.5

The default Failed Robotic Assignments work queue type is now Standard. In previous releases, the default type was Robotic. For usage information, see Configuring a work queue for robotic automation.

Upgrade impact

After upgrading to Pega Platform 8.5 and later, you cannot save case types in which you configure the Queue for robot smart shape to route new assignments to the Failed Robotic Assignments work queue. Existing assignments that you routed to the Failed Robotic Assignments work queue are not affected.

How do I update my application to be compatible with this change?

As a best practice, do not use the Failed Robotic Assignments work queue in your custom implementations. Instead, configure the Queue for robot smart shape to route new assignments to a Robotic work queue. When possible, update existing case types to use the robotic work queues that you created in your application.

Gadget configuration by using IAC gateway console is no longer supported

Valid from Pega Version 7.2.1

The Internet Application Composer (IAC) gateway was deprecated in Pega Platform™ 7.2.1 and is no longer supported. The IAC was used to embed a Pega Platform application, such as a gadget, on the pages of a web application that was located on your intranet, extranet, or internet site.

Upgrade impact

After an upgrade to Pega Platform 8.5, the configuration of gadgets through the IAC gateway console is no longer supported.

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

To make subsequent changes to your current web mashup, use Pega Web Mashup. 

For more information, see Tutorial: Creating a mashup with Pega Web Mashup.

Email Wizard support discontinued

Valid from Pega Version 8.4

Pega Platform™ no longer includes the Email Wizard. This wizard helped set up an email service for sending and receiving email in Pega Platform. The wizard generated an email account, an email listener, and an email service rule.

After an upgrade to Pega Platform 8.4 and later, existing clients must create new email accounts and email channels in App Studio. When you configure a new email channel, you add your email accounts so that customers can send and receive email by using the Pega Email Bot. Configuration of an email channel automatically generates an email listener and service email rules.

For more information, see Creating an email account and Building an Email channel.

Tamper-proof Pega Web Mashup loading

Valid from Pega Version 8.5

To protect your application from hackers, Pega Web Mashup is now loaded in a more secure way. The system generates a channel ID in the mashup code for validation on the server, before passing the mashup request. 

For more information, see Creating a mashup.

Upgrade impact

After an upgrade to Pega Platform 8.5, existing mashups, which do not have the channel ID parameter in their code, cannot load and users see the access control warning.

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

If you need to maintain full availability of the mashup during the upgrade of the production environment, perform the steps in Migrating existing mashups.

Deprecation of EAR deployments in Pega Platform 8.6

Valid from Pega Version 8.6

Starting with Pega Platform 8.6, EAR deployments of Pega Platform are deprecated. In the upcoming 8.7 release, EAR deployments will not be supported. The following rules that require EAR deployments will also be deprecated and no longer supported in Pega Platform 8.7:

  • Connect EJB
  • Connect JCA
  • JCA Resource Adapter
  • JMS MDB Listener
  • Service EJB

With this deprecation, you can use the latest tools and keep your application up to date. 

Upgrade impact

In Pega Platform 8.6, you can still create rules that require EAR deployments and update existing rules. However, after an upgrade to Pega Platform 8.7, rules that require EAR deployments are no longer supported.

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

To prepare your application for this change well in advance of the Pega Platform 8.7 release, see the following table for a list of alternative rules and for guidance on modernizing your application.

Deprecated rule typeAlternative rule typeRecommended configuration
Connect EJBConnect RESTSubstitute legacy EJB resources with a REST API, and use REST connectors to interact with them.
Connect JCAConnect RESTSubstitute legacy JCA resources with a REST API, and use REST connectors to interact with them.
JCA Resource AdapterJCA resource adapters are data records that are used within the scope of a Connect JCA rule. If you replaced Connect JCA rules in your application with Connect REST rules, JCA resource adapters are no longer relevant.No further configuration is necessary.
JMS MDB ListenerJMS ListenerReplace JMS MDB Listener configurations with standard JMS Listener configurations.
Service EJBService RESTRedefine your EJB services as a set of RESTful service APIs, and invoke them over HTTP/HTTPS.

For information on the supported platforms that are affected by this deprecation, see Pega Platform 8.6 Support Guide.

Legacy Parse XML rule configurations must be upgraded to edit them

Valid from Pega Version 8.6

If your application has Parse XML rules that use the legacy configuration from Pega Platform 5.x, you cannot edit these rules after you upgrade to Pega Platform 8.6 until after you upgrade them to use tree-based parse rule configuration.

You must upgrade a Parse XML rule that you want to edit if it shows the following warning when you open it in Dev Studio.

This type of Parse XML rule is deprecated. An upgrade should be performed.

An option to upgrade also displays below the message.

Upgrade impact

Parse XML rules with the legacy configuration do not map data to the clipboard, and the rule definition is empty. After you upgrade to Pega Platform 8.6, you cannot edit Parse XML rules that you created in Pega Platform 5.x or earlier until you upgrade them to use tree-based parse rule configuration.

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

Update legacy Parse XML rules to use tree-based parse rule configuration before you edit them in Pega Platform 8.6. Using tree-based parse rules is considered a best practice.

  1. Open the legacy Parse XML rule.
  2. On the Mapping tab, click Upgrade.
    Result: The Allow tree editing? check box is displayed and is automatically selected. You can add attributes and elements to the tree structure, or delete them.
  3. Save the upgraded rule configuration.

For more information, see Parse XML rules.

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