Import and export feature for generic decision data
Valid from Pega Version 7.2.1
New import and export functionality improves the management of generic decision data records (the records that do not belong to the Strategy Results class). You can now configure generic decision data records in a CSV file and later import that file to the Pega 7 Platform. You can also export the existing generic decision data record configuration from the Pega 7 Platform to a CSV file, and save that file in a directory that is external to the Pega 7 Platform.
For more information, see Decision data rule type enhancements.
Introduction of Customer Movie
Valid from Pega Version 7.2.1
Customer Movie provides the Event Catalog, where you can create multiple event types to collect customer data from specific input streams or batch uploads. This data is stored in a new type of data set called Event Store. Use the Customer Movie feature to make informed and personalized decisions for your customers, and to accelerate decisions.
For more information, see Creating an event in the Event Catalog.
Building custom mobile apps based on an explicit version of Hybrid Container
Valid from Pega Version 7.2.1
You can now lock the version of Hybrid Container on which your custom mobile app is built in Designer Studio. Locking the version helps avoid compatibility issues with the devices that are used in your organization. To lock the version of Hybrid Container, you must set the version in a .pyHCBuildVersion declare expression for a specific application.
For more information, see Building custom mobile apps based on a selected version of Hybrid Container.
Open cases in a mobile app with push notifications sent from Pega 7 Platform applications
Valid from Pega Version 7.2.1
Push notification smart shapes in a workflow of a Pega 7 Platform application can now send push notifications that open a case in a custom mobile app. Users working in the field can use this feature to instantly access priority assignments instead of having to search for changes manually.
For more information, see Configuring the Push Notification shape.
Improved security for clipboard pages
Valid from Pega Version 7.2.1
To prevent data leakage and inconsistency, the Pega 7 Platform does not allow properties on a clipboard page to refer to properties on pages with a lower scope. For example, an autopopulate property on a node type clipboard page cannot source data from a data page with scope “requestor” or “thread.”
For more information, see Page scope types for data and declare pages.
Child case queries can be slow after upgrade
Valid from Pega Version 7.2.1
After upgrading, performance might be slow when you run queries on child cases for work tables that existed prior to the upgrade. This issue is often indicated by PEGA0005 (query time exceeded limit) alerts that can be correlated to these queries in the logs. To resolve the issue, add a database index to each of your work tables by using a multicolumn index on the pxCoverInsKey, pxObjClass, and pyStatusWork columns.
For more information, see Performance improvements for child case queries.
Attribute-based access control model
Valid from Pega Version 7.2.1
Attribute-based access control (ABAC) is a security authorization model in which access rights are determined through the use of policies and attributes. A policy decision engine in ABAC evaluates digital policies against available data (attributes) to permit or deny access to the requested resource. For example, you can now determine access rights to cases by examining security attribute values assigned to the user and the case.
For more information, see Attribute-based access control.
Store and source content in Box
Valid from Pega Version 7.2.1
You can now attach content from Box while working on a case in your application. You can attach files directly to your case or include them in a Pulse message. You can also store all the case and Pulse attachments in your application in Box. To enable content sourcing and storage in Box, configure the Content sourcing and Content storage sections on the Integration & security tab of your application rule.
For more information, see Storing and sourcing content in Box.
Enhanced entity extraction with the CRF method
Valid from Pega Version 7.2.1
The Free Text Model rule now uses the Conditional Random Field (CRF) method for named entity extraction. The CRF method improves the accuracy of entity extraction by using sequence tagging and by reducing the number of false positives that were generated in the process of extracting named entities from the text. In addition, you can define your own custom entities and import them into the Pega 7 Platform as entity extraction rules that contain Rule-based Text Annotation (Ruta) scripts.
For more information, see Improved Free Text Model rule type.
Adjust case urgency in Case Designer
Valid from Pega Version 7.2.1
You can now provide an urgency when configuring the goal and deadline for a case type in Case Designer. By increasing the urgency of a case that has an expired service-level agreement, you can call attention to unresolved work in your application.
For more information, see Setting goals and deadlines for a case type.