Published Release Notes

MBeans deprecated in favor of Pega API

The use of MBeans for cluster management has been deprecated, although MBeans will continue to function for legacy deployments. The recommended best practice for automating system management is to use the Pega API. For more information, see Pega API.

Support for multiple custom mobile apps for a Pega Platform application

To enhance the user experience and provide support for native mobile components, you can create multiple custom mobile apps for a Pega Platform™ application. For each custom mobile app, you must create a different mobile channel interface. In addition, you can configure each custom mobile app to run only in a specific portal for an application. The custom mobile app uses this portal regardless of which default portal is defined for the access group.

For more information, see Selecting a portal for a custom mobile app.

Encrypt sensitive case data by using a secure default Pega Platform cipher and AWS KMS keys

You can encrypt sensitive data within your application without having to write custom cipher classes. You can configure encryption on the Data Encryption landing page by using your own keys managed in your private Amazon Web Services Key Management Service (AWS KMS) instance. Pega^® Platform encryption uses keys that are stored in AWS KMS to support both time-based and on-demand key rotation. Technical issues can arise in some cases, for example, if a key is deleted from AWS KMS.

For more information, see Potential problems with keystores when using AWS KMS, Configuring a Platform cipher, Types of ciphers.

Simplified deployment of stand-alone Apache Ignite servers

You can now install or upgrade Pega^® Platform in client-server mode, which uses Apache Ignite in a simplified way. The new installation process for stand-alone Apache Ignite servers does not require that you provide database credentials in a text file to communicate with Pega Platform nodes (clients). You provide this information by using JNDI support instead.

For more information, see Apache Ignite client-server clustering topology and the appropriate Deployment Guide.

Support for an external Elasticsearch cluster for on-premises deployments

On-premises customers can configure an Elasticsearch cluster that is external to the Pega Platform™ by using client-server mode. Using an external search configuration makes Elasticsearch more highly available and scalable. 

You can view the status of your external Elasticsearch service on the Search landing page. For more information, see link to Viewing the status of an external search service.

Integrated Application Security Checklist helps you deploy a secure application

Pega^® Platform now provides an Application Security Checklist that you can refer to when you prepare your application for deployment. By completing the recommended tasks in this checklist, you can track your progress, access instructional information for tasks, and verify that your configurations are secure.

For more information, see Preparing your application for secure deployment, Compliance Score tab, Designer Studio — Home page.

Change passwords from Pega Mobile Client

You can now change your Pega^® Platform password from a mobile device. After your password expires and you try to log in to a custom mobile app, Pega Mobile Client lets you define a new password and verifies it against active password policies.

For more information, see Enabling security policies.

Pega Digital Experience API for creating consumer-grade interfaces

You can use front-end frameworks such as React and Angular to create a user interface that is backed by the powerful business logic of Pega Platform™. The updated Pega Digital Experience API leverages the OpenAPI Specification to enable Pega Platform to work with the front-end framework of your choice.

Pega unit test suites are now modular

It is now possible to include test cases and test suites inside test suites. This feature makes test suites modular and improves the management of cases while creating, modifying, and executing them for regression testing.

For more information, see Pega unit test suites.

Archival support added to cases in Pega Cloud

You can now create an archival policy to move inactive cases from Pega Cloud to secondary storage. By periodically purging entries from your database, you can improve application performance.

For more information, see Case archiving.