Remove obsolete versions of the PredictiveAnalytics-UI and PredictiveAnalaytics-IntSvcs rulesets
Valid from Pega Version 7.2.2
After you upgrade the Pega 7 Platform to version 7.2.2, remove the PredictiveAnalytics-UI and PredictiveAnalytics-IntSvcs rulesets from your application as their versions are obsolete. Beginning with Pega 7.2.2, use the Pega-DecisionScience ruleset that contains the latest versions of the PredictiveAnalytics-UI and PredictiveAnalytics-IntSvcs rulesets.
For more information, see About ruleset versions.
Rule creation and simulations of changes in a change request in the Decision Manager portal
Valid from Pega Version 7.2.2
Two major enhancements to revision management give Decision Manager portal users more control over change requests. Revision managers and strategy designers can now create rule instances as part of a regular change request. They also can run data flows to do simulations of changes that are introduced by the change request.
For more information, see Rule creation and simulations of changes in a change request in the Decision Manager portal.
Language detection option in Text Analyzer
Valid from Pega Version 7.2.2
On the Text Analyzer form, you can identify the language of incoming records based on their language metadata tag by selecting the Language detected by publisher option. This option applies only to Text Analyzer rules that process Twitter records. By combining this option with the advanced language filtering criteria of Twitter data sets, you can filter out unnecessary data and analyze only the Twitter records that are relevant to your business objective.
For more information, see Configuring advanced filter conditions for Twitter data and Configuring language settings.
Facebook metadata types available for analysis
Valid from Pega Version 7.2.2
The number of Facebook metadata types available for analysis in your application through Facebook data sets has been extended. After you provide a valid page token that corresponds to your Facebook page, you can analyze the following metadata types that relate to that page: public posts, tagged posts, promoted posts, direct messages, and comments on posts. By analyzing these metadata types in your application, you can enhance your understanding of your customers' needs and respond to issues faster.
For more information, see Creating a Facebook data set record.
Options for filtering data in Twitter data sets
Valid from Pega Version 7.2.2
Twitter data sets have more options for filtering tweets. On the Advanced options tab of the Edit Data Set form, you can configure your Twitter data set to not analyze tweets if they contain specific keywords or if the tweets are made by specific authors. You can also select the languages to analyze based on the language metadata tag of the incoming tweets (tweets in other languages are ignored). By configuring the filtering criteria, you can ignore data that is not relevant to your text analysis and retrieve only the records that you need.
For more information, see Configuring advanced filter conditions for Twitter data.
Reconfiguration of the Adaptive Decision Manager service after upgrade to Pega 7.2.2
Valid from Pega Version 7.2.2
After you upgrade the Pega 7 Platform to version 7.2.2 from a version prior to 7.2,1, you need to configure the Adaptive Decision Manager service. Beginning with Pega 7.2.1, the Adaptive Decision Management (ADM) service is native to the Pega 7 Platform and is supported by the Decision data node infrastructure.
For more information, see Services landing page.
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.
Enhancing the performance of your Next-Best-Action strategy with globally optimized strategies
Valid from Pega Version 8.6
Starting in version 8.6, Pega Platform™ combines the versatility of Next-Best-Action Designer with strategy performance enhancements provided by using globally optimized strategies (GOS). Decrease the run time and memory usage of executing the Next-Best-Action strategy in batch or real-time scenarios by using the globally optimized strategies generated by Next Best Action Designer.
GOS is supported by Pega Platform's standard business change management process. GOS rules are automatically included in relevant revision packages.
For more information, see Enhance the performance of your Next-Best-Action strategy with globally optimized strategies (8.6).
Support for picklists with parameterized data pages in App Studio in Cosmos React UI
Valid from Pega Version 8.6
You can now use data pages with parameters to populate a property of the picklist type with filtered results in App Studio. For example, in a survey case type, you can use a parameterized data page to configure cascading drop-down controls in which the values in a secondary drop-down list are based on the value that the user selects in the primary drop-down list. With dynamically-sourced picklists, you get greater flexibility in configuring picklists, and users see more accurate values.
For more information, see link Dropdown control Properties — General tab.
Easier customer record management in Customer Profile Designer (early preview)
Valid from Pega Version 8.6
The new Customer Profile Designer module of Pega Customer Decision Hub™ makes it possible for marketing analysts and strategy designers to define the associated data for each customer context directly in the Pega Customer Decision Hub portal. It is also possible to define more complex associated data structures that use a custom data flow, or define associated data of different types, such as RDBMS and Cassandra, for the same customer context.
Customer Profile Designer is available in Pega Customer Decision Hub 8.6 version as an early preview version. The functionality will be further expanded in future releases.
For more information, see Manage customer records in Customer Profile Designer (8.6).