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.
Support for OAuth 2.0 authorization code grant type
Valid from Pega Version 8.1
Pega Platform™ now supports the OAuth 2.0 authorization code grant type, which allows Pega Platform to act as an OAuth 2.0 access token provider for native applications on mobile and other devices. By using the authorization code grant type for mobile clients, you no longer need to implement a variety of standards for various authentication providers. The authorization code grant type also supports the Proof Key for Code Exchange standard (PKCE) for securing public clients.
For more information, see Creating and configuring an OAuth 2.0 client registration.
Use client-based access control to support EU GDPR requirements
Valid from Pega Version 8.1
You can use client-based access control (CBAC) to satisfy the data privacy requirements of the European Union General Data Protection Regulation (GDPR) and similar regulations. By using client-based access control, you can identify the personal data of clients and automatically process requests to view, update, or remove the data in a secure manner. You can also enforce restrictions on the use of this data in application functions.
For more information, see Client-based access control.
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.
More quality metrics on the Application Quality dashboard
Valid from Pega Version 8.1
On the Application Quality dashboard, for each case type you can now view quality metrics such as guardrail score, test coverage percentage, unit test pass rate, list of guardrail of warnings, uncovered rules, and failed Pega unit tests. These metrics are also available for rules that are used in the application but that are not a part of any case type. To access these metrics, on the Application Quality dashboard list of case types, click Find issues.
For more information, see Application Quality landing page.
Test ID added to repeating dynamic layouts
Valid from Pega Version 8.1
A unique Test ID property has been added to repeating dynamic layouts to support automated testing, enabling you to write dependable automated tests against any Pega application. By including this unique identifier in your automated testing, you ensure a higher level of productivity and reliability within your applications.
For more information, see Test ID and Tour ID for unique identification of UI elements.
Autogenerated controls have unique IDs
Valid from Pega Version 8.1
Autogenerated controls have a unique ID by default. This unique ID ensures that the Document Object Model (DOM) is HTML5-compliant and avoids problems that can be caused by elements having the same ID. The setting to enable or disable unique IDs is on the HTML5 Application Readiness page.
For more information, see Unique IDs in autogenerated controls.