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.

Deprecated support for Pega Platform deployments on embedded Cassandra

Valid from Pega Version 8.6

If you use Pega Platform™ decision management capabilities, Pega Platform uses Cassandra as the underlying storage system for the Decision Data Store (DDS), which manages the Cassandra cluster and stores decision management data in a Cassandra database. Future versions of Pega Platform will no longer support deployments on embedded Cassandra. In Pega Platform version 8.6, deployments using embedded Cassandra are deprecated but still work. To ensure future compatibility, do not create any new installations using embedded Cassandra.


For information about how to configure Pega Platform to access an external database, see Defining Pega Platform access to an external Cassandra database.

Virtual questions deprecated in 8.6

Valid from Pega Version 8.6

Following the improvements in Pega Intelligent Virtual Assistant (IVA), the creation of virtual questions is now deprecated and planned for removal. To avoid additional effort during updates to future releases, do not use deprecated features. For optimal application performance and efficient development of conversation processes, you now collect information from users by using the Ask a question smart shape.

For more information, see Adding a case type conversation process for a conversational channel and Asking a question in a case.

Semantic URLs in Pega Platform

Valid from Pega Version 8.5

URL addresses for Pega Platform™ applications and application resources now appear as clear, meaningful paths. This enhancement helps users understand the structure of the application that they are using, which makes navigation quicker and more intuitive.

Loading cues in Pega Platform

Valid from Pega Version 8.6

Pega Platform™ applications that rely on the Cosmos React framework now feature a visual placeholder for the page that is being loaded. The system displays an indicator when loading portals, cases, simple pages, and list pages. This update provides users with a visual cue that their request is being processed, which improves the user experience.

Send event notifications in Pega Platform

Valid from Pega Version 7.3

You can configure applications to notify users of case changes or other significant events that occur in an application. Use notifications to engage application users by providing key updates that might be of interest to them.

You can deliver notifications over the default web gadget and email channels or use a custom channel that you created. You can configure multiple web gadgets to display different kinds of notifications. The email channel supports notification frequency of instant, daily, or weekly.

Application users can set their own notification preferences in the run-time portals or override the set preferences for a specific case type instance.

For more information, see Sending event notifications and Management of user notification preferences.

Cosmos React UI is now available in Pega Platform

Valid from Pega Version 8.5

Pega Platform™ now provides you with tools to develop React-based applications in App Studio. This enhancement, which was developed as part of Project Fnx, uses components that rely on the ReactJS library to power the Cosmos design system. The updated UI technology improves application performance, creates a better user experience, and provides greater flexibility for front-end developers by drawing from a well-established open-source technology.

In Pega Platform 8.5, Cosmos React UI is an opt-in beta. For more information about using Cosmos React UI in your application, see Previewing Cosmos React UI.

To learn about Project Fnx, see Project Fnx.

Legacy rules removed to reduce Pega Platform installation size

Valid from Pega Version 7.4

The installation of Pega® Platform 7.4 removes deprecated and unused rules. The smaller installation size decreases rule sync time and reduces the amount of storage required for Pega Platform. In addition, the smaller installation reduces the rule database size and shortens installation and upgrade times. You can access the legacy rules, if needed, in the PegaLegacyRules:01-01-01 in the Resource Kit on the Pega Platform media.

For more information see Finding legacy rules in sections.

Pega Survey documentation refers to deprecated field

Valid from Pega Version 7.2.1

The documentation for Pega® Survey refers to the Answer Layout field on the Complex Question form, but this field is no longer supported. For more information about the question layout formats that Pega Survey supports, see Pega Survey.

Support for large binary data item storage in Pega Mobile Client and offline case attachments in Pega Platform

Valid from Pega Version 7.4

Pega® Mobile Client can now store and synchronize large binary data items and their corresponding actions from the action queue on Android and iOS devices. As a result, custom mobile app users can view, attach, and delete data files, whether the device is online or offline. For this function to work, you must enable offline case attachment support, which allows your custom mobile apps to synchronize case attachments between the Pega Platform and the mobile device.

For more information, see Enabling offline case attachments support and Client Store API.

Tab groups are deprecated

Valid from Pega Version 7.3

Beginning with Pega 7.3, tab groups have been replaced with layout groups, which offer better performance and flexibility. Tab groups are based on the Yahoo User Interface (YUI) library, which is no longer supported on the Pega 7 Platform.

User interface rule forms now use layout groups instead of tab groups to place layouts in forms.

For more information, see Adding a Layout Group.

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