Third party models integration made possible by directly importing PMML in predictive models
Valid from Pega Version 7.1.7
Predictive models can now import models in PMML format. The PMML integration in predictive models allows you to use third party models without extra conversion and configuration. For more information on this new feature, see About Predictive Model rules.
Improved adaptive model accuracy
Valid from Pega Version 7.1.7
Enhancements have been made in the grouping scores method that is used to create the adaptive model outcome profile (also known as: classifier). Because scores form the base for calculating propensities, these changes make models more accurate. The enhanced grouping scores method is available with any new model generated in Pega 7.1.7 and does not require any changes to existing adaptive model rules or adaptive model components. For more information on adaptive models, see About Adaptive Model rules.
In-memory Adaptive Analytics Manager process
Valid from Pega Version 7.1.7
The new internal Adaptive Analytics Manager (ADM) process running in PRPC makes it possible to use adaptive analytics without the availability of the external ADM server. Although not a replacement for the external ADM server, it streamlines the design and development of applications making use of adaptive analytics. For more information on the configuration that allows your application to use the internal ADM process, see the Infrastructure Services landing page.
Delayed adaptive learning
Valid from Pega Version 7.1.7
Data flows, a new rule type in Pega 7.1.7, allow you to store adaptive inputs and interaction results for a given period of time when running a strategy. This makes it possible to capture and learn from responses at a later date. For more information on data flow design for delayed learning, see Data Flow rule form - Completing the Data Flow tab.
Decision data stores
Valid from Pega Version 7.1.7
Decision Management in Pega 7.1.7 introduces two new concepts to manage data: decision data stores, and Data Nodes (DNodes). Horizontally scalable, and supported by DNodes, decision data stores take data from different sources, and make it available for real time and batch processing. This infrastructure is managed through the DNode Cluster Management landing page.
Manage data from different sources using data sets
Valid from Pega Version 7.1.7
Data sets define collections of records, allowing you to set up instances that make use of data abstraction to represent information stored in different sources and formats. This new rule type introduces the ability to manage data in database tables, decision data stores, and Visual Business Director data sources. Standard Interaction History and Adaptive Manager data sets manage interaction results and adaptive model data. The DataSet-Execute method supports data management operations on records that are defined by the data set. For more information on this new rule type, see About Data Set rules.
Data flow orchestration
Valid from Pega Version 7.1.7
Data flows provide a pattern-guided design experience to orchestrate, combine and sequence data based on a set of instructions from source to destination. You can run and manage data flows using the Data Flows landing page. For more information on this new rule type, see About Data Flow rules.
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.
Noticeable differences between work objects created in the Decision Manager portal when compared to Designer Studio
Valid from Pega Version 7.1.7
In the Decision Manager portal, you create work objects by running flows in the enterprise application that serves as the base application for the application overlay. If the enterprise application does not include the UI-Kit-7 in its application rulesets, work objects can display differently in the Decision Manager portal when compared to Designer Studio because an application overlay is always configured to include the UI-Kit-7 ruleset.
Recommendation:
- Add the UI-Kit-7 ruleset dependency to the enterprise application.
- Redesign the user interface to comply with the UI-Kit-7 ruleset.
Rollback functionality is limited to latest revision
Valid from Pega Version 7.1.7
The rollback functionality in DSM Revision Manager allows customers to roll back the import of the latest revision to their DSM application. Only one rollback is allowed; after a rollback, the rollback option is disabled until the next revision is imported. If importing two (or more) revisions at once then attempting a rollback, the system only rolls back one revision.
Example: a user has a base DSM application. They import Revision 1, and then import Revision 2. Next, they try to roll back both revisions. The system reverts to the Revision 1 version of the application, and the customer cannot revert all the way back to the base application.