Published Release Notes

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.

Managed real-time data flow runs

Pega Platform™ now fully manages the life cycle of real-time data flow runs which helps you save time and reduce maintenance efforts. You no longer need to re-create the runs in every environment and manually pause and restart them after every modification. The application manages such runs by seamlessly implementing your changes and keeping the runs active until they encounter a specified number of errors or until you exclude the runs from the application.

For more information, see Tutorial: Using managed data flow runs and Creating a real-time run for data flows

Configuring geolocation tracking at the case level

You can now enable geolocation tracking at a case level to track users of an offline-enabled custom mobile app. By tracking users who are working on a case, you can monitor or supervise them while they are using the custom mobile app and when the app is running in the background. You can also track users when the device is not connected to the server. Recorded locations are synchronized with the server and stored in a database that is available through a data page. When Pega Platform™ receives location data, the new Map control can display multiple user tracks and markers that represent other data, for example, job locations that are assigned to users.

For more information, see Tracking mobile end users with the Map control and Adding the map control.

REST APIs for system management

New REST APIs are available for reports, agent management, requestor management, cache management, queue processing, and node management. Call these APIs to troubleshoot issues, or perform administrative functions in Cloud applications.

For more information, see Pega API.

Define participants for case types

You can now configure participants more easily for case types. By defining case participants, you can indicate their relationship with a case and share important case updates with them. You can update case participants at run time, route assignments and approvals to them, and send notifications to them when goals and deadlines are not met.

For more information, see Participant configuration for case types.