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.

Enhanced run-time behavior of the currency and number controls

Valid from Pega Version 8.6

The currency and number controls now display separators at run time, even as the user types the values. When the user enters more than three digits, a locale-dependent separator immediately groups the digits into thousands in real time. For example, when a user who is based in the U.S. types 100000, the input field displays the number as 100,000. The currency control additionally displays currency symbols at all times, whether the input field is in focus or not.

This enhancement improves clarity and the user experience because the user no longer needs to move away from the field to see the formatting of the input, and typing long strings of numbers is now more convenient.

For more information, see Controls.

Theme management in Cosmos React

Valid from Pega Version 8.6

App Studio now features an updated interface for managing the look of the theme in Cosmos React environments. The theming page enables you to quickly rebrand the theme's component library by selecting fonts, colors, and logos, while also displaying a live preview of the UI. This enhancement provides a more intuitive way to adjust the presentation options in your React-based application, which saves development time and encourages prototyping and experimentation.

For more information, see Defining themes in Cosmos React

Support for configuring and saving external data in App Studio

Valid from Pega Version 8.6

You can now configure a savable data plan to easily replace or update related data directly from App Studio, and persist those changes during the case lifecycle. This enhancement allows you to work directly in App Studio, without being limited to read-only access of data from case types.

Automation performance enhancements

Valid from Pega Version 8.6

To improve the performance of automation-based REST services and DX APIs, you can now configure JSON inputs and outputs in automation rules. The automation passes the JSON object directly to an automation-based REST service or DX API, eliminating the need to transform data on a page to JSON first. You can also take advantage of this enhancement if you are calling an automation from an activity. Additionally, you can simulate a JSON response in the automation rule and update the JSON sample if needed.

For more information, see <link TBD> and <link TBD>.

Cosmos React-UI supports custom authentication

Valid from Pega Version 8.6

Pega Platform™ now supports custom authentication in applications that use Cosmos React-UI. Depending on the needs of your users and the functionality of your application, you might need to write custom authentication schemes to meet specific requirements. 

Clients that use custom authentication in their applications can now take advantage of the Cosmos React-UI.

For more information, see Securing Cosmos React-UI applications.

Support for creating automations

Valid from Pega Version 8.6

You can now create automations in Pega Platform. By creating an automation, you clearly define a contract to perform a specific task. For example, you can create an automation that retrieves a list of data objects that are available in the application.  

For more information, see Creating an automation.

Support for filtering requests and responses in activity-based REST services

Valid from Pega Version 8.6

You can now use a JSON data transform to filter inputs and outputs in activity-based REST services. With this enhancement, you maintain high performance by filtering unnecessary properties from the REST service request and response.

For more information, see Creating a request for POST, PUT, and PATCH methods by using an activity implementation and Creating a response for Service REST methods by using an activity implementation.

Tracer file size limit to prevent disk usage issues

Valid from Pega Version 8.6

The maximum size of files with event details that Tracer generates is now 10 GB to avoid excessive disk usage and performance issues. Tracer applies the size limit at the node-level, so every node that runs in your system can use up to 10 GB of disk space to create an output file with event details. As a result, you can monitor the health of your system and deliver issue-free applications without experiencing disk space problems.

For more information, see:

Support for configuring data sources by using OpenAPI Specification

Valid from Pega Version 8.6

The Integration Designer in App Studio now supports OpenAPI Specification. You can provide an OpenAPI Specification endpoint or upload a YAML file to automatically generate data sources according to the specification. With this enhancement, you avoid having to manually create a representative sample JSON request and response, saving you time and increasing productivity.

For more information, see Integrating with a REST API by using OpenAPI Specification.

Integration and security tab now divided into two tabs

Valid from Pega Version 8.6

The Integration and Security tab is now two separate tabs on the Application Definition form: Integration and Security. While the content of these two tabs are related, they function more effectively as separate tabs. The Security tab now includes the Authentication section, so you can add existing authentication services to your Application Definition to more effectively manage the security of your application. 

For more information, see Security tab of the Application Definition.

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