Control group configuration for predictions
Valid from Pega Version 8.5
You can now configure a control group for your predictions in Prediction Studio. Based on the control group, Prediction Studio calculates a lift score for each prediction that you can later use to monitor the success rate of your predictions.
For more information, see Customizing predictions.
Response timeout configuration for predictions
Valid from Pega Version 8.5
You can now set a response timeout for your predictions in Prediction Studio. By setting a response timeout, you control how Prediction Studio registers customer responses that later serve as feedback data for your predictions.
For more information, see Customizing predictions.
Unable to create text analytics models when Java 2 Security is enabled
Valid from Pega Version 7.3
Security exceptions that prevent you from creating text analytics models are caused by the Java 2 Security feature that is enabled at the JVM level. This feature denies access to the text analytics resources that are required for text parsing functions.
Creating a text analytics model results in a failure because of a number of security-related exceptions, for example:
java.security.AccessControlException: Access denied ("java.lang.RuntimePermission""createSecurityManager")
The suggested approach for avoiding this problem is to use the text analytics models that are provided by default, for example, pySentimentModels, pyTelecomTaxonomy, and so on.
For more information, see Text Analyzer.
Delegation experience in revision management
Valid from Pega Version 7.3
Revision managers can now control rule authoring by assigning a delegation experience to any rule that is part of a revision management change request. Delegation experience types offer different rule authoring capabilities, so the revision manager can select the appropriate delegation experience for the task and the strategy designer’s experience.
Deploy revisions directly in target environments
Valid from Pega Version 7.3
As a revision manager, you can now directly deploy or migrate completed revisions to multiple Pega 7 Platform environments that were configured as targets by the system architect. The revision management process is faster because you do not need to package a revision as a JAR file, and then manually import that file to the Pega 7 Platform. Additionally, this solution gives business users more control over application rulesets and enables them to act more independently.
For more information, see Direct deployment of revisions.
Decision Analytics portal replaces Predictive Analytics Director portal
Valid from Pega Version 7.3
The Decision Analytics portal replaces the Predictive Analytics Director (PAD) portal, the Text Analytics landing page, and the Adaptive Models Reporting landing page. In this new work area for predictive analytics and text analytics, the business scientist can control the full model life cycle by building predictive models, importing PMML models, building sentiment analysis and text classification models, creating and monitoring adaptive models, and updating any existing models.
For more information, see Overview of the Decision Analytics work area.
Improved diagnostics and logging for Decision Data Store nodes
Valid from Pega Version 7.3
On the Decision Data Store tab, you can view additional metrics from the Decision Data Store nodes that help with diagnosing Cassandra database problems. You can also set the logging level to control interactions from and to Decision Data Store nodes.
For more information, see Decision Data Service node status information and Configuring the Decision Data Store service.
Tracing Cassandra queries in a Decision Data Store data set
Valid from Pega Version 7.3
You can now enable the Trace option for every operation in the Decision Data Store data set to collect information about how the Decision Data Store queries are executed in Cassandra. You can view this information in the clipboard and use it to troubleshoot and optimize performance of the Decision Data Store data sets and Decision Data Store nodes. All the queries and related events are collected on the DDSTraces page on the same Pega thread.
For more information, see Tracing Decision Data Store operations.