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.

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.

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.

PegaWAI ruleset deprecated in 8.5

Valid from Pega Version 8.5

Accessibility functions that were contained in the PegaWAI ruleset are now integrated into the main Pega Platform™. Consequently, the user interface in your applications now features accessibility functions out of the box, so you no longer need to use the PegaWAI ruleset to ensure accessible behavior in your application.

For more information, see Building an accessible UI.

External data flow rules are deprecated

Valid from Pega Version 8.5

External data flows are now deprecated and no longer supported. To improve your user experience with Pega Platform™, the user interface elements associated with these rules are hidden from view by default. Identifying unused features allows Pega to focus on developing and supporting the features that you need.

For more information, see Deprecated: External data flows.

Enhancing your revision management process with Deployment Manager pipelines

Valid from Pega Version 8.5

Pega Platform 8.5 offers improved synergy between revision management and the automated deployment process provided by Pega's Deployment Manager 4.8 pipelines. Use Deployment Manager 4.8 to increase the efficiency of business-as-usual application changes and automatize the deployment of revision packages.

For more information, see Managing the business-as-usual changes.

Removal of Pega Mobile Client 7

Valid from Pega Version 8.5

You can now use a single Pega Mobile Client™ that improves app performance, app development, and meets all your mobile needs. With the introduction of new functionalities for mobile apps, Pega Mobile Client 7 is removed in Pega Platform™ 8.5.

Upgrade impact

After an upgrade to Pega 8.5, you can no longer build mobile apps based on Pega Mobile Client 7, and existing apps based on Pega Mobile Client 7 no longer connect to Pega Platform. App developers can now configure mobile apps with Pega Mobile Client.

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

Existing clients that upgrade to Pega 8.5 are automatically switched to Pega Mobile Client.

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.

Merge application-level test reports by using the Pega API service

Valid from Pega Version 8.5

A new REST API is now available so that you can merge test coverage reports at the application level without having to perform this task manually. This service accepts the application IDs for the test coverage reports that you want to merge and generates a consolidated report in the target application provided.

For more information about setting up your environment and making API calls with Deployment Manager, see the Documentation/readme-for-swagger.md file in the DeploymentManager04_08_0x.zip file, found in the Deployment Manager download package.

Triage cases archiving in the email bot (Pega Cloud Services)

Valid from Pega Version 8.5

For Pega Platform™ that is installed in Pega Cloud® Services, you can configure Pega Email Bot™ to archive resolved triage cases that are older than a specified number of days. Archiving triage cases improves the overall performance of your system by reducing the primary storage consumption and cost because the system places such resolved triage cases in a secondary storage.

For more information, see Archiving resolved emails for an email bot (Pega Cloud Services).

Declarative Network Viewer tool uses Pega components

Valid from Pega Version 8.5

The Declarative Network Viewer tool now uses out-of-the-box Pega components. In earlier releases, the tool relied on Adobe Flash Player, which is gradually being phased out of modern browsers. This enhancement maintains the original functionality, while ensuring product and technological continuity.

For more information, see the Declarative Network Viewer article in the Pega Marketplace.

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