Convert data instances into decision parameter rules
Valid from Pega Version 7.1.8
The Convert groups wizard is available in the Hierarchy landing page when the list of your propositions include decision data records.
Click Convert groups at the top of the landing page to use the wizard and to convert data instances into decision parameter rules. This conversion is necessary to make the existing proposition data instances available for revision management.
Update to the Data Flows rule
Valid from Pega Version 7.1.8
It is now possible to collect statistics for each active data flow. These include the number of processed records, records that caused errors and last processed records per shape, as well as historical throughput measured for the entire data flow.
There are two new patterns in the Data Flow rule:
- Event Strategy - define this pattern to use an event strategy in a data flow and to connect a data stream and static data sources to an event strategy.
- Filter - specify filter conditions and apply them to each element of the input flow
Apart from this, the Merge pattern was updated to execute the flow when there is no data on the secondary branches and the Strategy pattern allows you to specify the class where you want to store your strategy results.
New Dynamic System Setting for proposition management
Valid from Pega Version 7.1.8
A new Dynamic System Setting affects the process of creating new groups on the Proposition Management landing page.
When the PropositionManagement/isOnlyVersionedProposition parameter is set to true, users can only create the versioned propositions.
When the PropositionManagement/isOnlyVersionedProposition parameter is set to false, the Create Group dialog allows users to create either the versioned or unversioned propositions (the Create versioned proposition data check box and the Decision data rule section are both displayed).
New form of the HBase rule
Valid from Pega Version 7.1.8
There is a new form of the HBase rule. While you cannot create any new instances of the Pega 7.1.7 HBase rule, legacy instances in your application remain functional. You can still use the Pega 7.1.7 instances of the HBase rule, but you cannot make changes to them.
New data sets
Valid from Pega Version 7.1.8
There are three new types of data sets:
- HDFS Data Set, which reads and saves data from external, distributed Apache Hadoop file systems.
- HBase Data Set, which supports HBase storage.
- Stream Data Set, which processes the continuous data stream of events.
Real-time processing of data flows
Valid from Pega Version 7.1.8
It is possible to run, manage, and monitor data flows that use stream as their data source. You can create a new run from the Real-time processing landing page.
Predictive models can drive predictions
Valid from Pega Version 8.6
You can use predictive models as the basis of your predictions. As a data scientist, you can now use Machine Learning Operations (MLOps) to replace models in your system. You can replace a model in a prediction with a PMML, H2O MOJO, or Pega OXL predictive model, as well as a scorecard or field, and then approve the update for deployment to a production environment. You can respond to a Prediction Studio notification that an active model does not generate enough lift and decide to replace the low-performing model with a high-accuracy model. You can also update a prediction on a regular basis, for example, whenever you develop a new churn model in an external environment.
For more information, see Replace models in predictions and migrate changes to production with MLOps.
Enhancing the performance of your Next-Best-Action strategy with globally optimized strategies
Valid from Pega Version 8.6
Starting in version 8.6, Pega Platform™ combines the versatility of Next-Best-Action Designer with strategy performance enhancements provided by using globally optimized strategies (GOS). Decrease the run time and memory usage of executing the Next-Best-Action strategy in batch or real-time scenarios by using the globally optimized strategies generated by Next Best Action Designer.
GOS is supported by Pega Platform's standard business change management process. GOS rules are automatically included in relevant revision packages.
For more information, see Enhance the performance of your Next-Best-Action strategy with globally optimized strategies (8.6).
Support for picklists with parameterized data pages in App Studio in Cosmos React UI
Valid from Pega Version 8.6
You can now use data pages with parameters to populate a property of the picklist type with filtered results in App Studio. For example, in a survey case type, you can use a parameterized data page to configure cascading drop-down controls in which the values in a secondary drop-down list are based on the value that the user selects in the primary drop-down list. With dynamically-sourced picklists, you get greater flexibility in configuring picklists, and users see more accurate values.
For more information, see link Dropdown control Properties — General tab.
Easier customer record management in Customer Profile Designer (early preview)
Valid from Pega Version 8.6
The new Customer Profile Designer module of Pega Customer Decision Hub™ makes it possible for marketing analysts and strategy designers to define the associated data for each customer context directly in the Pega Customer Decision Hub portal. It is also possible to define more complex associated data structures that use a custom data flow, or define associated data of different types, such as RDBMS and Cassandra, for the same customer context.
Customer Profile Designer is available in Pega Customer Decision Hub 8.6 version as an early preview version. The functionality will be further expanded in future releases.
For more information, see Manage customer records in Customer Profile Designer (8.6).