SystemCleaner agent is split into node-level and cluster-level agents
Valid from Pega Version 7.3
The Pega-RULES:SystemCleaner agent has been split into node-level and cluster-level agents to avoid database performance issues. The new node-level agent, Pega-RulesEngine:NodeCleaner, runs on all the nodes in the cluster, while the new cluster-level agent, Pega-RulesEngine:ClusterAndDBCleaner, runs on only one node in the cluster. If you customized the agent schedules of the Pega-RULES:SystemCleaner agent, you must manually update the agent schedules of the new agents because customized schedules are not retained.
For more information, see Agent schedule data instances – Completing the Schedule tab.
Fallback activity for Service REST and SOAP
Valid from Pega Version 7.3
You can now configure a fallback response activity for a time-out for Service REST and SOAP. Using a fallback response activity makes it easier to meet a service-level agreement (SLA) by providing a logical response in a timely manner. For example, the fallback activity can display a default offer to an ATM customer instead of an offer that is based on that particular customer's data.
For details about configuring the fallback response activity, see Service REST form - Completing the Service tab and Service SOAP form - Completing the Service tab.
Add custom controls to section palettes
Valid from Pega Version 7.3
You can add custom controls to the Basic or Advanced palettes in sections. With this enhancement, Pega® Platform developers have easy access to custom controls. The check box is available in the HTML tab of the custom control rule. You can add a custom icon to display in the menu with the custom control.
For more information see Adding custom controls to the section palette in Designer Studio.
Select multiple nodes for the Adaptive Decision Manager service
Valid from Pega Version 7.3
You can select multiple Pega Platform nodes and assign them to the Adaptive Decision Manager (ADM) service as worker nodes. Adaptive learning is no longer restricted to a single server, which provides resilience and scalability. You can add or remove nodes from the ADM service while the system processes customer responses.
For more information, see Changes to Adaptive Decision Manager.
Greater cluster stability with client-server clustering topology
Valid from Pega Version 7.3
You can now deploy Pega® Platform in the new client-server clustering topology that uses Apache Ignite, which increases stability in large clusters and provides independent scalability for both servers and clients. This technology separates the client nodes, which are responsible for Pega Platform processes, from the server nodes, which are responsible for cluster communication and distributed features. If your production environment consists of more than five nodes in the cluster, it is recommended that you switch to the new client-server topology.
For more information, see Apache Ignite client-server clustering topology and the appropriate Deployment Guide.
Performance enhancements to the Visual Business Director data set
Valid from Pega Version 7.3
When you create instances of the Visual Business Director data set, you can specify the granularity of data aggregations and select dimension levels to reduce the Visual Business Director memory footprint and query time. In addition, the Actuals Visual Business Director data set on the Data-pxStrategyResult class has been replaced with a regular Decision Data Store instance. You can now quickly update or synchronize records in the Actuals data set with the Interaction History data set.
For more information, see Data Set rule form - Completing Data Sets and Aggregation on the Visual Business Director data set.
Visual Business Director service renamed to Real Time Data Grid service
Valid from Pega Version 7.3
To avoid confusion in the Pega Marketing application, the Visual Business Director service has been renamed to Real Time Data Grid service.
For more information, see Real Time Data Grid service.
Improved adaptive model configuration and management
Valid from Pega Version 7.3
The usability of the Adaptive Model rule form has been improved by changes to the tabs and settings. Performance monitoring of Adaptive Model rules is now done through the new Decision Analytics workspace for business scientists. The Adaptive Models Management landing page has adapted to the new multinode architecture and displays the values for the number of outstanding responses and the time of the last update. Additionally, you can manually initiate updates from the Adaptive Models Management landing page.
For more information, see Changes to Adaptive Decision Manager.
Today widget for iOS custom mobile apps
Valid from Pega Version 7.3
The Pega Mobile Client has been extended to support a Today widget in custom mobile apps for iOS. By default, the Today widget displays the current user's list of work objects. This functionality is available only for offline-enabled custom mobile apps and requires that your certificate set include a widget provisioning file.
For more information, see Configuring a Today widget on iOS.
Base a case type on an existing case type
Valid from Pega Version 7.3
When creating a case type in your application, you can now select an existing case type or class on which to base the new type. The new case type reuses assets from the existing type. When building on a strategic application, you can define the class in which the new case type is created to ensure that the case type has the correct pattern inheritance.
For more information, see Creating a case type.