Improve application test coverage by running multiple sessions
Valid from Pega Version 8.1
You can improve the test coverage of your application by using a new test coverage method - Application Coverage. Multiple users can perform coverage sessions which are aggregated into a single report. By using report metrics that show the number of rules that are covered and are not covered by tests, developers can identify which areas of the application need more test coverage.
For more information, see the Test Coverage landing page.
REST APIs added for management of agents and requestors
Valid from Pega Version 8.1
You can use new REST APIs to download a module version report or manage requestors and agents in Pega Platform™. For example, you can use a requestor REST API to end a requestor process, and you can use an agent REST API to start or stop an agent. These APIs allow external systems to report and manage Pega resources.
For more information, see Pega API for Pega Platform and Pega API.
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.
Use repositories as sources for File data sets
Valid from Pega Version 8.1
You can configure remote repositories, such as Amazon S3 or JFrog Artifactory, or a local repository, as data sources for File data sets. By referencing an external repository from a File data set, you enable a parallel load from multiple CSV or JSON files, which removes the need for a relational database for transferring data to Pega Platform™ in the cloud.
For more information, see Creating a File data set record for files on repositories and Configuring a remote repository as a source for a File data set.
Apache Ignite is no longer supported
Valid from Pega Version 8.1
Apache Ignite is no longer supported and has been replaced by Hazelcast Enterprise Edition 3.10 in embedded mode. If you used encryption with Apache Ignite, you can configure encryption on Hazelcast Enterprise Edition in the same way that you configured it for Apache Ignite.
For more information about encrypting nodes, see Enabling encrypted communication between nodes.
Define a taxonomy by using the Prediction Studio interface
Valid from Pega Version 8.1
Create a topic hierarchy and define keywords for each topic in Prediction Studio faster and more intuitively than by editing a CSV file. If you have already defined a taxonomy in a CSV file, you can import that file and modify existing topics and keywords by using the Prediction Studio interface.
For more information, see Creating-keyword-based topics for discovering keywords and Tutorial: Configuring a topic detection model for discovering keywords.
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.
REST API now fetches the latest version of Application Quality metrics
Valid from Pega Version 8.1
When you request Application Quality metrics by using the REST service, the service requests a refresh of the metrics. This means that you always get the latest version of the metrics and can decide whether your application is ready for deployment based on that information.
For more information, see Pega API.
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.
Start and stop a coverage session by using the REST API
Valid from Pega Version 8.1
You can now start and stop application-level test coverage by using REST services. You can use the results of the coverage session for gating purposes in a release pipeline.
For more information, see Pega API.