Published Release Notes

Support for when rule in offline-enabled applications

You can use when rules in offline-enabled applications without creating custom JavaScript code. Using when rules reduces the offline-enabled application implementation time by further automating case processing in offline mode and deriving the logic directly from the model. No additional configuration is required to use when rules in offline mode.

For more information, see When rule support in offline mode.

Case type landing page is created automatically

When you create a case type, a landing page is created automatically. You can add this page to the main menu, operator menu, and mobile tabs. You no longer need to create this page manually.

Support for an external Elasticsearch cluster for on-premises deployments

On-premises customers can configure an Elasticsearch cluster that is external to the Pega Platform™ by using client-server mode. Using an external search configuration makes Elasticsearch more highly available and scalable. 

You can view the status of your external Elasticsearch service on the Search landing page. For more information, see link to Viewing the status of an external search service.

Define time conditions for pausing a process in App Studio

You can now pause a process in App Studio until a date or time is reached or a certain amount of time has passed. By defining the conditions that pause a process, you can create dependencies among cases in your application.

For more information, see Pausing a process in a case.

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

Additional adaptive model predictors based on Interaction History

Customer interactions are now automatically used in adaptive models to predict future customer decisions. For example, a phone purchase registered in Interaction History allows an adaptive model to predict that a customer is more likely to accept supplementary coverage for a new device. Such interactions, collected in a predefined Interaction History summary, are applied as an additional set of predictors in an adaptive model.

The aggregated Interaction History summary predictors are enabled by default for every adaptive model configuration.

For more information, see Enabling Interaction History predictors for existing adaptive models.

Update text analytics models instantly through an API

Use the pxUpdateModels API to automatically retrain text analytics models for which you gathered feedback as a result of the pxCaptureTAFeedback activity. The pxUpdateModels API provides an option to update the model with the latest feedback without having to open Prediction Studio. Instead, you can use the activity from your application, for example, through a button control.

For more information, see Feedback loop for text analytics.

New integration system resource

You can now define integration systems that you can use when you create data pages, integration connectors, and databases. Integration systems are associated with an icon that is displayed on the Integration Designer so that you can quickly view the systems that are used by your data types. This information is useful for assessing the effect of migrating to a new system of record and for understanding your data model.

For more information, see Creating an integration system.

Autogenerated controls have unique IDs

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.

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.