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.

Improved UI accessibility

Valid from Pega Version 8.6

Pega Platform™ now supports W3C Web Accessibility Initiative guidelines more fully, which creates a better user experience for people who rely on assistive technologies, such as screen readers.

The user interface now features the following enhancements:

  • Improved keyboard navigation and updated ARIA attributes for layouts, including dynamic, repeating, and table layouts.
  • Updated navigation for AJAX and dynamic containers.
  • More precise keyboard navigation and focus control for pop-up components, such as SmartTips.
  • Fixed accessibility gaps in out-of-the-box actionable controls and form components, such as buttons and text fields.
  • More accessible error messages with improved color schemes and focus control.
  • Accessibility code included in the Pega Platform ruleset by default, without the need for additional configuration.

For more information, see Supported keyboard navigation.

Improved scroll functionality in vertical tabs

Valid from Pega Version 8.6

When you scroll content in an application that uses the Cosmos theme, the UI now remembers the scroll position even if you switch between vertical tabs, for example, in the case details section. Previously, the application reset the page to the topmost position every time you switched tabs. This update improves the user experience by reducing context switching.

Addition of Servlet Management

Valid from Pega Version 8.6

Pega Platform™ now has Servlet Management in Pega Cloud® Services, which provides a simple and secure way to make changes to Pega Platform servlet definitions.

Servlet Management provides Pega Cloud Service clients with solutions to manage servlet configurations with self-service options. This reduces the cycle time for delivering configuration changes in Pega Cloud Service installations while also improving upgrade reliability

For more information, see Servlet management.

Upgrade impact

Clients with no application servlet customizations will not experience an impact. If you upgrade from Pega Platform version 8.5 or earlier and, prior to the upgrade, the Pega Cloud team provided your application servlet customizations, then following the upgrade, you must manually add, remove, or modify your servlet customizations in your upgraded application using this servlet management landing page in Pega Platform.

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

To manually move your pre-upgrade servlet customizations as appropriate or add new ones to your upgraded application using the new servlet management landing page, follow the steps in Adding a servlet.

Text predictions simplify the configuration of text analytics for conversational channels

Valid from Pega Version 8.6

Enable text analytics for your conversational channels, such as email and chatbot, by configuring text predictions that manage the text models for your channels. This new type of prediction in Prediction Studio consolidates the AI for analyzing the messages in your conversational channels in one place and replaces the text analyzer rule in Dev Studio.

Through text predictions, you can efficiently configure the outcomes that you want to predict by analyzing the text in your channels:

  • Topics (ticket booking, subscription cancellation, support request)
  • Sentiments (positive, neutral, negative)
  • Entities (people, organizations, airport codes)
  • Languages

You can train and build the models that predict these outcomes through an intuitive process, and then monitor the outcomes through user-friendly charts.

For more information, see Predict customer needs and behaviors by using text predictions in your conversational channels.

Upgrade impact

Channels that you configured with text analyzers in the previous version of your system continue to work in the same manner after the upgrade to the current version. When you edit and save the configuration of an existing channel, the text analyzer rule is automatically upgraded to a text prediction. The associated text prediction is now an object where you can manage and monitor the text analytics for your channel. When you create a new channel in the upgraded system, the system automatically creates a text prediction for that channel.

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

  1. Enable the asynchronous model building and reporting in text predictions through job schedulers that use the System Runtime Context (SRC) by adding your application to the SRC.
    For more information, see Automating the runtime context management of background processes.
  2. Enable model building in text predictions by configuring background processing nodes.
    For more information, see Assigning decision management node types to Pega Platform nodes.

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.

External data flow rules are removed

Valid from Pega Version 8.6

In previous versions of Pega Platform™, you could configure data flows to run in an external Hadoop environment. The external data flows functionality was deprecated and hidden from view in Pega Platform 8.5. The functionality has been now removed and is no longer available in Pega Platform 8.6.

For more information, see External data flow rules are deprecated.

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.

Connect MQ rules configured with alias queue do not work after upgrade

Valid from Pega Version 8.6

Connect MQ rules that you defined with an alias queue in earlier versions of Pega Platform do not work after an upgrade to Pega Platform 8.6.

Upgrade impact

If you defined an alias queue in Connect MQ rules, after an upgrade to Pega Platform 8.6, those Connect MQ rules do not work.

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

In the Pega-IntegrationEngine ruleset, create the following dynamic system settings and their default values:

  • "mq/pmo" = 0
  • "mq/gmo" = 0
  • "mq/oo_request" = 1040
  • "mq/oo_response" = 16

For more information, see Creating a dynamic system setting.

Embedded properties in DX API v2 requests are no longer removed

Valid from Pega Version 8.6

In Pega Platform version 8.5, when you use the POST and PATCH v2 DX API methods with an embedded page property included in the content element of the request, the system removes all properties in the embedded page that are included in the case but are not a part of the request. Now, the merge logic has been modified to update embedded page fields sent up in the request, and keep other fields unchanged.

This feature simplifies client code and prevents data corruption.

Data Management

Valid from Pega Version 7.1.3

Improvements to data handling were made for the Data Pages, autopopulate properties, and reference properties.  Lightweight lists were optimized.

  • Property references are now maintained on the Work Page.
  • PageList properties can reference a Data Page.
  • Auto-populate properties can be used in a seciton to show results from a Data Page.
  • Data Pages can run in “Page” mode as well as “List” mode
  • The "Rules Not Using Lightweight List" report was enhanced.
  • A PageList property that references a Data Page may be used to populate a grid.
  • Related autopopulated properties can now be referenced.

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