Published Release Notes

Improve application test coverage by running multiple sessions

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.

Security fields in JFrog Artifactory repository rule form removed

The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not functional in Pega Platform™ 7.3, 7.3.1, and 7.4. This section has been removed from the JFrog Artifactory repository rule form in Pega Platform 8.1.

DCO Compatibility tool is deprecated

The DCO Compatibility tool has been deprecated. Use the Application Guardrails landing page to see the compliance score and any warnings for your application.

For more information, see Application Guardrails landing page.

Identify team members working on a rule

By using the team collaboration widget, you can see who on your development team is working on the rule that you are viewing. This widget is displayed in the section header when you are using the Case Designer, Data Designer, or Channels and interfaces configuration pages. When you update a page, a notification is sent to other collaborators stating that the content has been updated and prompting them to refresh to see the latest content.

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.

Troubleshooting offline-enabled applications in a browser

You can now troubleshoot offline-enabled applications by using the Tracer tool and developer tools that are available in a web browser. You can troubleshoot scripts that are running when the application is running, without having to use additional debugging tools.

For more information, see Application debugging using the Tracer tool, Troubleshooting offline-enabled applications with the Tracer tool in a browser, and Offline capability.

@java and locatable pages no longer supported

@java and locatable pages are no longer supported. Existing rules that use @java and locatable pages will continue to work; however, changes to these rules cannot be saved unless @java and locatable pages are replaced by supported functionality. Use a rule utility function (RUF) instead of an @java page, and use a data page instead of a locatable page. In addition, Pega Platform™ displays a guardrail warning when you open a rule that uses an @java page or a locatable page.

REST API now fetches the latest version of Application Quality metrics

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

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

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.