Published Release Notes

Test ID added to repeating dynamic layouts

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.

Customize the subject line for case emails

You can now customize the subject line for emails that are sent from cases when an assignment is routed to a worklist and when you configure the Send Email shape. You can reference field names in the subject line to make it more meaningful. By customizing the subject line, you can call attention to cases that require action.

For more information, see:

• App Studio – Enabling case notifications and Sending email from a case
• Dev Studio – Enabling case notifications and Sending email from a case

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.

Data entered in a new harness is lost after a sync operation

If you create a case in an offline-enabled application and enter data in a new harness, this data is lost after you click Submit and the sync operation takes place. For more information, see Offline capability and Enabling offline support for cases.

Post private messages in Pulse

You can now post messages in Pulse to initiate conversations with selected users within a context. By posting private messages, you can discuss specific topics with relevant users without broadcasting them to all users.

For more information, see:

• App Studio – Posting a message in Pulse
• Dev Studio – Posting a message in Pulse

Reference spaces and documents in Pulse

You can now reference spaces and documents when you post Pulse messages. By including a link in your Pulse message that opens a relevant space or application document, you can add context to a conversation.

For more information, see:

• App Studio – Adding a reference in Pulse
• Dev Studio – Adding a reference in Pulse

Define a taxonomy by using the Prediction Studio interface

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.

Improvements to automatic routing in the Email channel

To provide a broader range of use cases for a conversational channel developer, several new routing criteria have been added to the Email channel configuration. You can use detected language, a when rule, and keyword-based entities in the routing criteria when you set up the intelligent email routing capability for an Email channel.

For more information, see Intelligent routing and Configuring routing conditions for automatic email handling.

Use spaces to collaborate with users

You can now collaborate with other users in your application on a specific area of interest by using spaces. By restricting the discussion of certain topics to the users of a space, you can avoid broadcasting irrelevant messages to all users in your application.

For more information, see:

• App Studio – Collaborating with users by using spaces
• Dev Studio – Collaborating with users by using spaces

Resolve child cases with the parent case

You can now configure a stage to resolve open child cases when the parent case is resolved. Resolving child cases on the resolution of the parent case ensures that no child cases are left open when the parent case reaches the end of its life cycle.

For more information, see:

• App Studio – Configuring case resolution
• Dev Studio – Configuring case resolution