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.
User interface distortions in the Decision Manager portal
Valid from Pega Version 7.1.6
By default, the New Application wizard in Pega 7.1.6 configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Decision Manager portal. Both applications created in previous maintenance level updates and applications created in Pega 7.1.6 that do not include the UI-Kit-7 dependency are not impacted by this known issue.
Workaround:
- Open the application record.
- In Application Rulesets, remove UI-Kit-7.
- Save the application record.
User interface distortions in the Predictive Analytics Director portal
Valid from Pega Version 7.1.6
By default, the New Application wizard configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Predictive Analytics Director portal. Applications created in maintenance level updates previous to Pega 7.1.6, and applications that do not include the UI-Kit-7 dependency, are not impacted by this known issue.
Workaround:
- Open the application record.
- In , remove UI-Kit-7.
- Save the application record.
App Studio enhancements further support Pega Express methodology
Valid from Pega Version 8.6
App Studio now includes improvements that you can use to plan your Microjourney™ in a more convenient way. The Overview workspace now includes a button to edit application details, such as name, description, and business objectives, without having to switch to Dev Studio. You can also access relevant information faster, because Case Designer displays additional details about channels, data objects, and attachments associated with a case type directly in a properties pane. For improved management of your features, feature categories are now available in the application inventory so that you can clearly communicate to your development team what type of features need implementation.
For more information, see:
- Editing application details in App Studio
- Associating personas with channels
- Adding features to application inventory
- Creating a Microjourney for customer success
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.