Published Release Notes

Support for native search in custom mobile apps

To improve the overall user experience in a custom mobile app, you can configure native search in the user interface of the application. To use the search capability, first configure the pySearchConfiguration rule. This rule allows you to optionally define a set of search categories as a local data source. You then configure the mobile search action for any user interface control, for example, a button in a section. Users can tap the search field to see the most recent search results, including results that are grouped by categories, as they enter search text.

For more information, see Native search capability in custom mobile apps and Configuring search in custom mobile apps.

Multi-answer questions available for surveys

Pega Platform™ now supports multi-answer questions for all types of surveys. You can use multi-answer questions to collect multiple answers from users. For example, you can ask users to list all the languages that they speak by selecting multiple check boxes.

For more information, see Designing a survey.

Enhanced Pulse performance and layout on mobile devices

Pulse performance is now faster on mobile devices. The user interface has been enhanced to enable better collaboration among users. The new Pulse mobile layout provides a better user experience for posting messages, adding attachments, bookmarking content, and so on.

For more information about Pulse, see:

• App Studio – Communicating with users by using Pulse
• Dev Studio – Communicating with users by using Pulse

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.

Ability to edit and copy data from an email to case properties for an Email channel

The procedure for triaging an email case has been improved to help automate the process and to ensure that the case data is always up-to-date and accurate. The system can pull data, such as a date, name, or an address, out of the received email or its attachments, and automatically assign the data to a spun-off business case property. To help the system learn, you can highlight using a color, edit entity types, and map entity types for an email triage case to business case properties. You can also update cases with new properties, if triage cases are identified as duplicates and contain new detected properties. Each mapped entity type is marked in different color and an entity map legend helps you identify what each color represents.

For more information, see Email triage and Defining suggested cases for the Email channel.

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.

Archival support added to cases in Pega Cloud

You can now create an archival policy to move inactive cases from Pega Cloud to secondary storage. By periodically purging entries from your database, you can improve application performance.

For more information, see Case archiving.

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.

Resolve Job Scheduler and Queue Processor rules with the AsyncProcessor requestor type

Use the new AsyncProcessor requestor type to define a default dynamic context to resolve background rules such as Job Scheduler and Queue Processor rules. Switch to an application-based context after you create your own access groups, to resolve only the rules that are included in your application.

For more information, see AsyncProcessor requestor type.

Relevant records management shows more information

Relevant records for a class now include more information that you can use to manage the records for your application development. As a result of these enhancements, you can:

• View inherited and inactive relevant records for the specified class.
• Mark specific records as active or inactive for the specified class.
• Mark specific records as relevant on the rule form.

You can use these new details to filter the list of relevant records for a class on the Relevant Records tab of the selected class. For more information, see Managing relevant records and Marking records as relevant records.