New shapes in the Event Strategy rule type
Valid from Pega Version 7.2.1
The Event Strategy rule type supports branching and merging of the data stream by using the new Split and Split and Join strategy shapes. You can now split your event strategy into several paths to identify multiple types of events with a single rule instance.
In addition, the Lookup shape replaces the Static Data shape. You can add static data anywhere in the strategy. For example, you can filter out irrelevant events, and then evoke static data for only the events that are relevant to the strategy.
For more information, see Event Strategy rule type enhancements.
State management support for data flows that run event strategies
Valid from Pega Version 7.2.1
You can now store the state of your data flow work items that contain event strategies in the Cassandra database of the decision data store. With this solution, you can recover the event strategy state without any loss of data. You can also pause and resume active data flows that invoke event strategies.
For more information, see Event Strategy rule type enhancements.
Support for data rollback and commit in service-enabled system management
Valid from Pega Version 7.2.1
You can use the service-enabled manage tracked data tool to roll back or commit data that has been imported with the service-enabled import tool.
The service-enabled manage tracked data tool lets you commit imported data or roll back all non-committed data instances to their state immediately prior to when they were imported. The tool only tracks and supports rolling back data instances that do not belong to the PegaRULES database name (Data-Admin-DB-Name).
For more information, see Rolling back and committing tracked data.
Extended proposition filter functionality
Valid from Pega Version 7.2.1
Multiple enhancements to the Proposition Filter rule type extend the functionality of proposition filters. When you configure the filter or the default behavior criteria in a proposition filter rule, you can select a strategy rule that contains an External Input shape. You can also apply the default behavior criteria to all incoming propositions that do not match the business issue or group defined in a proposition filter rule. Additionally, you can view the labels of when and strategy rules when you configure the filter or default behavior criteria.
For more information, see Proposition filter usability enhancements.
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.
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.
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.
Support for Twitter data recovery
Valid from Pega Version 7.2.1
You can configure a Twitter data set to use the new playback option to recover tweets that the system could not retrieve during a period of time in which tweets were unavailable, such as during a data flow failure. You can specify the time period for which you want to retrieve Twitter data and enter the maximum number of tweets that you want to retrieve.
For more information, see Improved Free Text Model rule type.
Time-based retrieval of Facebook posts
Valid from Pega Version 7.2.1
You can now control the amount of data that is retrieved from Facebook data sets by using the new search functionality for Facebook data set records. You can limit the retrieval of posts to any number of past weeks, days, hours, or minutes to get only the data that is relevant to your business objective or that you lost as a result of a system outage or failure.
For more information, see: Improved Free Text Model rule type.