Flexible inputs in strategies
Valid from Pega Version 7.1.6
Decision parameters allow business users to influence the decision through flexible inputs that do not require changing strategies. System architects use extension points to configure the data model and user interface supporting decision parameters. Decision parameters are used in strategies, and changes to the values of decision parameters become immediately available without requiring any changes to the strategy.
The rule pxRunDecisionParameters supports the use of decision parameters through activities.
Enable business users to own parts of an enterprise application
Valid from Pega Version 7.1.6
Decision Manager functionality allows business users to own parts of an enterprise application within the boundaries defined by IT. PegaDM includes the Pega-DecisionManager ruleset that supports this functionality.
System architects define the boundaries for business users in the Decision Manager portal using revision management and proposition authorization facilities in Designer Studio. Access control is provided through custom roles, which system architects can create based on granular privileges. The Decision Manager portal provides business users with a controlled environment for the workflow, and the activities necessary to address the objectives of a revision.
Predefined inputs when designing and testing strategies
Valid from Pega Version 7.1.6
External input settings allow for propagating results to other strategies, providing strategy designers with a mechanism to reuse strategies and test strategies with predefined inputs.
Design segmentation trees in strategies
Valid from Pega Version 7.1.6
You can include the traditional segmentation tree pattern in your strategies using the following features:
- Exclusion components to conditionally stop the propagation of decision results.
- Split components to branch the decision results according to the percentage of cases covered by the result.
- The Otherwise label for component connections where one of the outgoing connections has a defined label.
Simplified Adaptive Decision Manager Deployment
Valid from Pega Version 7.1.6
The Adaptive Decision Manager (ADM) server relies on automatic detection of the database dialect. This simplifies the number of deployable archives used to set up the ADM service.
Cumulative calculation in strategies
Valid from Pega Version 7.1.6
Iteration components provide strategies with a mechanism to perform cumulative calculations.
Predictive models monitoring
Valid from Pega Version 8.2
In Prediction Studio, you can now monitor the predictive performance of your models to validate that they make accurate predictions. Based on that information, you can re-create or adjust the models to provide better business results, such as higher accept rates or decreased customer churn.
For more information, see Monitoring predictive models.
Kafka custom serializer
Valid from Pega Version 8.2
In Kafka data sets, you can now create and receive messages in your custom formats, as well as in the default JSON format. To use custom logic and formats for serializing and deserializing ClipboardPage objects, create and implement a Java class. When you create a Kafka data set, you can choose to apply JSON or your custom format that uses a PegaSerde implementation.
For more information, see Creating a Kafka data set and Kafka custom serializer/deserialized implementation.
Additional configuration options for File data sets
Valid from Pega Version 8.2
You can now create File data sets for more advanced scenarios by adding custom Java classes for data encryption and decryption, and by defining a file set in a manifest file.
Additionally, you can improve data management by viewing detailed information in the dedicated meta file for every file that is saved, or by automatically extending the filenames with the creation date and time.
For more information, see Creating a File data set for files on repositories and Requirements for custom stream processing in File data sets.
Simplified testing of event strategies
Valid from Pega Version 8.2
Evaluate event strategies by creating test runs. During each run, you can enter a number of sample events with simulated property values, such as the event time, the event key, and so on. By testing a strategy against sample data, you can understand the strategy configuration better and troubleshoot potential issues.
For more information, see Evaluate event strategies through test runs.