Data page unit test case setup and cleanup
Valid from Pega Version 7.2.1
You can now use one or more data pages, data transforms, or activities to set up a clipboard page with the appropriate properties before you run a data page unit test case. You can also use activities to create any required test data, such as work or data objects.
After you run a data page unit test case, the data pages that were used to set up the test environment are automatically removed. You can now also apply additional data transforms or activities to clean up the clipboard.
For more information, see Setup and cleanup of data page unit test cases.
New assertions for data page unit test cases
Valid from Pega Version 7.2.1
You can now configure the following assertions for data page unit test cases:
- Result count assertions for page lists, page groups, value lists, and value groups
- Unordered list and ordered list assertions for page lists
The Pega 7 Platform now supports these assertions in addition to expected run-time assertions for the data page and property assertions for any property type.
For more information, see Data page unit test case assertions.
New options to manage proposition validity
Valid from Pega Version 7.2.1
Manage your decisioning strategy more effectively with proposition validity settings. You can now set your propositions as always active, inactive, or active only within a defined time period. Setting a validity period for your propositions helps you to plan your strategy and automatically activate or deactivate propositions in the future.
For more information, see Proposition validity.
Define adaptive model context
Valid from Pega Version 7.2.1
You can define model identifiers in the Adaptive Model rule instance, which serve as partitioning keys, by selecting properties from the top-level SR class of your application. The Adaptive Decision Manager (ADM) server uses model identifiers to create adaptive models that use the same configuration, but collect different adaptive statistics. Use model identifiers in the Adaptive Model rule to create adaptive models for your purposes.
For more information, see the Context tab on the Adaptive Model form.
Execute Tests service to run all data page unit test cases
Valid from Pega Version 7.2.1
You can now use the Execute Tests service to run a set of tests at the end of build runs. An external validation engine, such as Jenkins, calls the service, which runs all data page unit test cases in your application, and returns the results in XUnit format. Use this service to validate the data in your application and to correct any issues before you deploy your application.
For more information, see Running all data page unit test cases with the Execute Tests service.
DSM rulesets become part of the PegaRULES application
Valid from Pega Version 7.2.1
The Pega-DecisionArchitect, Pega-DecisionEngine, Pega-BigData, and Pega-NLP rulesets were moved from the PegaDM application record to the PegaRULES application record. This change makes decision management functionality available for Pega 7 Platform users by default without any additional configuration required.
For more information, see DSM rulesets become part of the PegaRULES application.
HDFS data sets support Parquet files
Valid from Pega Version 7.2.1
The Parquet file format has been added to the list of supported file formats for data storage in the Hadoop Distributed File System (HDFS) data set record. On the Pega 7 Platform, you can now access an HDFS data set that stores data in the Parquet file format and perform various operations on that data set.
For more information, see Big Data enhancements in decision management.
New rule type: External Data Flow
Valid from Pega Version 7.2.1
You can now create External Data Flow rules on the Pega 7 Platform. By using this rule type, you run predictive models outside of the Pega 7 Platform and directly in the external Hadoop data set infrastructure. Processing large amounts of data on an external infrastructure improves overall performance on the Pega 7 Platform by reducing data transfer between the Hadoop cluster and the platform.
For more information, see Big Data enhancements in decision management.
New graphical framework for the Event Strategy rule form
Valid from Pega Version 7.2.1
The Event Strategy rule form introduces a new graphical framework that includes redesigned strategy shapes, improved navigation, and faster response time when building a strategy. These changes contribute to creating a more functional and engaging environment that allows strategy designers to successfully develop and maintain event strategy rules.
For more information, see Event Strategy rule type enhancements.
New shapes in the Event Strategy rule type
Valid from Pega Version 7.2.1
The Event Strategy rule type supports branching and merging of the data stream by using the new Split and Split and Join strategy shapes. You can now split your event strategy into several paths to identify multiple types of events with a single rule instance.
In addition, the Lookup shape replaces the Static Data shape. You can add static data anywhere in the strategy. For example, you can filter out irrelevant events, and then evoke static data for only the events that are relevant to the strategy.
For more information, see Event Strategy rule type enhancements.