Support for Apache Cassandra
Valid from Pega Version 7.3.1
The Pega® Platform can now read data from and write data to an Apache Cassandra database. Apache Cassandra is a NoSQL database that you can use when a NoSQL database better meets your scalability and processing requirements.
For a list of supported and unsupported features, see Apache Cassandra support.
Expose properties in Decision Data Store
Valid from Pega Version 7.3.1
You can now expose properties in Cassandra-based Decision Data Store data sets. With this solution, you can update single properties in extended customer analytic records (XCAR) without having to update the full customer record.
For more information, see XCAR in Decision Data Store.
Enhancements to bulk editing options for unversioned propositions
Valid from Pega Version 7.3.1
Bulk editing options for unversioned propositions have been enhanced to allow the use of Excel for editing. You can export and import unversioned propositions into Excel by using the Import wizard. Additionally, data types replace decision tables as the new storage format for unversioned propositions.
For more information, see Data type management and Proposition management enhancements.
Reuse existing propositions across applications
Valid from Pega Version 7.3.1
You can reuse existing propositions from built-on applications by using a new wizard to copy proposition groups across applications. This wizard gives you more options and flexibility when you define the business hierarchy in your application.
For more information, see Proposition management enhancements.
Requestor pools management in Designer Studio
Valid from Pega Version 7.3.1
On the new Requestor Pools landing page, you can view and manage requestor pools across the cluster, including on the current node and remote nodes. By using this landing page, you can tune the requestor pools to improve the performance of services. You can clear the requestor pool for a service package and view the requestor pool basic metrics and configured thresholds.
For more information, see Requestor pools management, Clearing a requestor pool, Viewing details for a requestor pool, Tuning a requestor pool configuration.
Migrate DDS data across various schema versions
Valid from Pega Version 7.3.1
You can use multiple versions of a single Decision Data Store (DDS) data set type in different applications that run on the same Pega® Platform instance and efficiently move data across those versions even if the underlying data schema is different. This solution improves the data management process and simplifies the reuse of existing data.
For more information, see Decision Data Store migration.
Support for PMML version 4.3 in predictive models
Valid from Pega Version 7.3.1
You can now leverage predictive models in the Predictive Model Markup Language (PMML) version 4.3 by importing them into predictive models on Pega® Platform. Pega Platform utilizes a large part of the PMML standard with the exception of some PMML 4.3 features that are not supported in the Predictive Model rule.
For more information, see Support for PMML version 4.3 in predictive models and Creating a predictive model.
Module version report generated from Designer Studio
Valid from Pega Version 7.3.1
From the new Class Management landing page, you can generate the module version report that provides information about classes in your system, module versions, and version creation dates. You can generate the report for all the nodes in the cluster or for a selected node that is either current or remote. The report is useful for debugging system problems because it helps identify the module version that is causing problems on a specific node.
For more information, see Module version report.
Emit remaining event strategy data at the end of a data flow run
Valid from Pega Version 7.3.1
Data flows have been updated to prevent data loss in event strategies. By default, when a batch or a real-time data flow stops and it contains an event strategy with Tumbling windows, all of the events that are in the Tumbling windows are emitted. Event emission triggers further processing in the event strategy, like aggregations and joins.
For more information, see Enhancements to data flows that contain event strategies and Event Strategy rule form - Completing the Event Strategy tab.
New aggregation functions in event strategies
Valid from Pega Version 7.3.1
You can use new functions in event strategies to build standard and complex aggregations. With new aggregation functions you can detect additional patterns in streams of data and deliver actionable insights.
For more information, see Adding aggregations in event strategies.