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.
Easy access to proposition-related rules when creating change requests in revision management
Valid from Pega Version 7.2.1
When selecting propositions for change requests in Decision Strategy Manager, you can view the proposition filter, strategy, and when rules that are associated with the decision data the selected propositions belong to. In addition, you can include those rules in change requests. To view and add any associated rules to a change request, the rules must be part of the application overlay. With the ability to view and select all proposition-related data, you can consistently revise not only propositions themselves but also all associated rules.
For more information, see Proposition-centric revision management functionality.
Dynamic System Setting for selecting clipboard pages implementation
Valid from Pega Version 7.2.1
Create the dsm/clipboard/optimize Dynamic System Setting to select which clipboard pages to use for strategies and data flows in all contexts. Without this setting or with its value set to true, strategies and data flows work on DSM clipboard pages. When you set the value to false, strategies and data flows work on the conventional Pega 7 Platform clipboard pages. This Dynamic System Setting allows you to configure run strategies consistently and obtain consistent results.
For more information, see DSM clipboard pages implementation.
The UpdateAdaptiveModels agent causes an exception after Pega 7.2 to 7.2.1 upgrade
Valid from Pega Version 7.2.1
After the Pega 7 Platform is upgraded from version 7.2 to 7.2.1, the log files might show an error that is caused by the UpdateAdaptiveModels agent. This agent is enabled by default and is responsible for updating scoring models in the Pega 7 Platform. If you use adaptive models in your solution, you can avoid this error by configuring the Adaptive Decision Manager service. If you do not use adaptive models, disable the UpdateAdaptiveModels agent.
For more information, see Configuring the Adaptive Decision Manager service and Pega-DecisionEngine agents.
Reconfiguration of the Adaptive Decision Manager service after upgrade to Pega 7.2.1
Valid from Pega Version 7.2.1
After you upgrade the Pega 7 Platform to version 7.2.1, you need to reconfigure the Adaptive Decision Manager service. Beginning with Pega 7.2.1, the Adaptive Decision Management (ADM) service is native to the Pega 7 Platform and is supported by the Decision data node infrastructure.
For more information, see Services landing page.
Support for predictive models in PMML version 4.4
Valid from Pega Version 8.5
Pega Platform™ now supports the import of predictive models in Predictive Model Markup Language (PMML) version 4.4. With this feature, you can import PMML models that use the anomaly detection algorithm.
For a list of all supported PMML models, see Supported models for import.
Limits on active data flow runs
Valid from Pega Version 8.5
You can now configure a maximum number of concurrent active data flow runs for a node type. Set limits to ensure that you do not run out of system resources and that you have a reasonable processing throughput. If a limit is reached, the system queues subsequent runs and waits for active runs to stop or finish before queued runs can be initiated, starting with the oldest.
For more information see, Limit the number of active runs in data flow services (8.5).
Upgrade impact
If you have many data flow runs active at the same time, you might notice that some of the runs are queued and waiting to be executed.
What steps are required to update the application to be compatible with this change?
You do not have to take any action. After the active runs stop or finish, the queued runs start automatically. The default limits are intended to protect your system resources, and you should not see a negative impact on the processing of data flows. However, if you want to allow a greater number of active data flow runs to be active at the same time, you can change the limits. For more information, see Limiting active data flow runs.