Published Release Notes

Ability to restrict access to the Import wizard

You can now restrict access to the Import wizard so that users implement an automated pipeline to deploy changes between environments such as staging and production. Deployment Manager is one method by which to create pipelines. By using pipelines to propagate changes, users can apply a standardized and automated deployment process for migrating their applications.

For more information, see:

• Ensuring that users migrate applications with a pipeline by restricting the Import wizard
• Understanding model-driven DevOps with Deployment Manager

Custom DX API attributes for auto-generated controls

Auto-generated controls now include the option to add custom attributes for use with the Pega Digital Experience (DX) API. The attributes are part of the DX API response to the front end and you can use them to modify the run-time behavior of the UI elements in your application. For example, you can add an attribute to a field that displays a tooltip text for that field at run time. This enhancement introduces significant flexibility to application development and gives you greater control over UI components.

For more information, see Adding custom attributes for version 1 DX API to auto-generated controls.

Access PegaUnit compliance metrics from a centralized location

PegaUnit compliance metrics and execution rate have been added to the PegaUnit metrics tile of the Application Quality dashboard. This dashboard provides a centralized location for all PegaUnit data for a specific application. 

The dashboard also supports granular PegaUnit test information for each case type and data type, similar to the process currently available on the branch quality dashboard. 

For more information, see Analyzing application quality metrics. 

More quality metrics on the Application Quality dashboard

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.

Set the status of a case on stage entry

You can now set the status of a case when it enters a stage. By setting the status of a case on stage entry, you can communicate to stakeholders how close a stage is to resolution. For example, if a case is in the approval stage, you can set the status of the case to "Under review" when the case enters the stage.

For more information, see:

• App Studio – Changing the status of a case
• Dev Studio – Changing the status of a case

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.

Click, record, and play UI scenario tests

You can now record, edit, and run scenario-based UI tests in end-user portals. By using scenario-based tests, developers focus on testing an application's ability to deliver real business value instead of writing code. Developers can test autogenerated and custom controls, actions, and navigation in a specific case or in an entire portal. Test recording is available on the run-time toolbar, and tests are available on a unified landing page that provides easy access to them. For more information, see Find and fix issues by using the Accessibility Inspector.

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.

Quality metrics now include charts with trends

The Application Quality landing page now contains charts that show changes in metrics over time. Landing pages for Test coverage and Unit testing also contain interactive charts with user-defined date range filters. The default date range of the charts is 2 weeks, but you can change it by using the Application: Quality Settings landing page. The historical data provided by the charts shows changes in application quality metrics over time, so that you can recognize trends and identify potential problems with application quality.

For more information, see Application Quality landing page.

New landing page allows you to customize the presentation of quality metrics

From the new Application: Quality Settings landing page, you can specify which built-in apps to include for testing. You can also modify the date range for graphs on the Application Quality, Application: Test coverage, and Application: Unit testing landing pages. Additionally, you can specify how many days the tests are considered current to be included on the Application Quality dashboard and in reports. By configuring how quality metrics are displayed, you can customize data presentation according to your needs, which can help improve the quality of your application.

For more information, see Application: Quality Settings landing page.