MBeans deprecated in favor of Pega API
Valid from Pega Version 8.1
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
Valid from Pega Version 8.1
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.
Support for an external Elasticsearch cluster for on-premises deployments
Valid from Pega Version 8.1
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.
Pega Digital Experience API for creating consumer-grade interfaces
Valid from Pega Version 8.1
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
Valid from Pega Version 8.1
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
Valid from Pega Version 8.1
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.
Fetch quality metrics for Pega unit tests by using the REST API
Valid from Pega Version 8.1
You can use the REST API to fetch quality metrics for the Pega unit tests of your application, such as unit test compliance, unit test execution results, test coverage, and guardrail compliance.
You can use the metrics returned by the service for gating purposes in a release pipeline.
For more information about the Pega API, see Pega API for Pega Platform.
Ability to search case attachments in Pega Cloud Services
Valid from Pega Version 8.1
File repositories in Pega Cloud Services are now indexed. Indexing allows your application users to search case attachments from end user portals based on content and metadata.
Parameter page is automatically removed after each Pega unit test run
Valid from Pega Version 8.1
The parameter page is automatically removed after each Pega unit test run. The reliability of subsequent tests is increased because they are not influenced by leftover parameter values that were set by the previous test.
For more information, see Cleaning up your test environment.
Import only new instances of specific classes
Valid from Pega Version 8.1
To bypass updates for specific classes and only import new instances of those types, edit the product rule definition. For more information, see Specifying product rule deployment options.