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.
Changes to Pega alerts that are related to Decision Data Store
Valid from Pega Version 7.3
The PEGA0085 alert informs users about insufficient disk space allocated for the Cassandra database. The PEGA0074 alert has been deprecated, and the PEGA0075 alert has been renamed and modified to include settings from the PEGA0074 alert.
For more information, see PEGA0074 alert, PEGA0075 alert, and PEGA0085 alert.
Improved diagnostics and logging for Decision Data Store nodes
Valid from Pega Version 7.3
On the Decision Data Store tab, you can view additional metrics from the Decision Data Store nodes that help with diagnosing Cassandra database problems. You can also set the logging level to control interactions from and to Decision Data Store nodes.
For more information, see Decision Data Service node status information and Configuring the Decision Data Store service.
Tracing Cassandra queries in a Decision Data Store data set
Valid from Pega Version 7.3
You can now enable the Trace option for every operation in the Decision Data Store data set to collect information about how the Decision Data Store queries are executed in Cassandra. You can view this information in the clipboard and use it to troubleshoot and optimize performance of the Decision Data Store data sets and Decision Data Store nodes. All the queries and related events are collected on the DDSTraces page on the same Pega thread.
For more information, see Tracing Decision Data Store operations.
Create pre-import and post-import steps
Valid from Pega Version 7.3
To take specific actions based on archive metadata, add pre-import and post-import action steps to collections. For example, you can configure a pre-import activity to automatically verify that an archive meets certain criteria before you import the archive. If the archive does not meet the criteria, Pega® Platform does not import the archive.
For more information, see Pre-import and post-import collections.
Rollover policy for log files
Valid from Pega Version 7.3
The rollover policy for log files is now based on time (daily) and file size (maximum file size is 250 MB). Log files are rolled over daily or when the maximum file size is reached. Current (not rolled over) log files do not have a time stamp. The time stamp is added when the log file is rolled over. In addition, the log file name for the current log file does not include the date. You can add the date to the current log file; however, the log file will not be rolled over. In addition, the web.temdir variable for setting the log file location is no longer supported; use the pega.logdir variable instead.
For more information, see Pega Platform logging with the Log4j 2 logging service.
Enhanced functionality of the Decision Manager portal
Valid from Pega Version 7.3
The Decision Manager portal now provides more revision management options. The Decision Analytics work area for development of predictive, adaptive, and text analytics models is now part of the Decision Manager portal. PegaUnit testing of rules is more convenient from a new Automated Testing landing page. Revision managers can reassign change requests back to strategy designers or other users of the Decision Manager portal without losing changes that were already made.
For more information, see Enhancements to the Decision Manager portal.
Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade
Valid from Pega Version 7.3
If you used node classification in Pega® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type. Agent schedules for standard Pega Platform agents are deleted and re-created with the new node type name, but any customization that you made in Pega 7.2.2 is not saved. You must manually update the agent schedules for standard Pega Platform agents in Pega 7.3.
For more information, see Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3 and the appropriate Deployment Guide.
Use Kafka data sets in Pega Decision Strategy Manager
Valid from Pega Version 7.3
You can create Kafka data set rules to connect to an external Apache Kafka server cluster and use this data set in decision management for processing real-time streaming data. Integrating Kafka data sets into complex event processing (CEP) as part of Event Strategy rules provides a fault-tolerant and scalable solution for processing real-time data feeds.
For more information, see Kafka data sets in decision management.