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.
Improved monitoring of data flow runs
Valid from Pega Version 7.2.1
To monitor the status, progress, and statistics of a data flow run, open it on the Data Flows landing page. Use the run and distribution details to report on data flow progress and possible service-level agreement (SLA) breaches. Run details are available at the node and partition level. Component-level statistics are available for the run, nodes, and partitions.
For more information, see the Data Flows landing page.
Adaptive learning without using an interaction ID
Valid from Pega Version 7.2.1
When you configure the Strategy shape in a data flow to capture the response to previous decisions, you do not have to provide an interaction ID. Instead, during the process of adaptive learning, adaptive models can query the Event Store data set over a specified period of time to retrieve decisions that were made for each response. This way, you eliminate the need to store the interaction ID on the client side.
For more information, see Delayed learning of adaptive models.
Single point of entry for decision management services configuration
Valid from Pega Version 7.2.1
Use the Services landing page to configure and monitor the Decision Data Store, Adaptive Decision Manager, Data Flow, and Visual Business Director services. This method simplifies decision management configuration because you can manage these services in one place.
For more information, see Services landing page.
Adaptive Decision Manager service in the Pega 7 Platform
Valid from Pega Version 7.2.1
The Adaptive Decision Management (ADM) service is now native to the Pega 7 Platform and is supported by the Decision data node infrastructure. Because of this enhancement, you no longer need to manage the ADM service as an external service. In addition, the ADM service does not require dedicated hardware or operating system environments.
For more information, see Services landing page.
Data Flow service in the Pega 7 Platform
Valid from Pega Version 7.2.1
The Data Flow service configuration on the Services landing page now provides a single point of entry for enabling running data flows in batch and real-time modes. To configure the Data Flow service, you must add Decision data nodes on which to run data flows and specify the number of Pega 7 Platform threads that are assigned to process the data flow runs. Additionally, as part of the Data Flow service, you can view the number of active data flows on each node.
For more information, see Services landing page.
HTML5 Visual Business Director (VBD) Planner
Valid from Pega Version 7.2.1
Visual Business Director (VBD) planner has a new look and is now available as an HTML5 web-based application, which replaces the VBD applet version. The new user interface is more intuitive and improves the user experience. You can open the HTML5 version of the planner on all supported browsers (Chrome, Firefox, Internet Explorer 11, and Safari).
For more information, see Visual Business Director.
Dynamic System Setting for partitioning Interaction History
Valid from Pega Version 7.2.1
Partition keys are used to optimize the retrieval and reading of records that are stored in the Interaction History data set. To define the number of partitions and partition keys for interactions that are recorded in the Interaction History data set, provide a positive integer value for the interactionHistory/numberOfPartition Dynamic System Setting.
For more information, see Interaction History partitions.
Simultaneous editing of propositions in revision management
Valid from Pega Version 7.2.1
When you refine proposition data in Decision Strategy Manager, you can now delegate various propositions that belong to a single decision data rule (for example, multiple propositions from a specific issue or group) to different users. These users can simultaneously edit the proposition data that was assigned to them (the same proposition cannot be part of two open change requests). With this solution, users can modify the proposition data independently, without locking the entire decision data rule for other users while the proposition data is being revised. The ability to view and select all proposition-related data makes it possible to consistently revise not only propositions themselves, but also all associated rules.
For more information, see Proposition-centric revision management functionality.