Export and import operations for data sets
Valid from Pega Version 7.2.2
You can move data between data sets and Pega 7 Platform instances more easily with export and import operations. You can use the export operation to prepare a backup copy of data outside the Pega 7 Platform. The import operation facilitates initialization of new Pega 7 Platform environments by providing a prepared set of data. You can export data from the data sets that support the Browse operation, and you can import data into the data sets that support the Save operation. Export and Import operations are not available for stream data sets such as Facebook, Stream, Twitter, and YouTube.
For more information, see Exporting data from a data set and Importing data into a data set.
Use Kerberos credentials in a Pega application to authenticate and access external systems
Valid from Pega Version 7.2.2
Authentication services now support Kerberos as an authentication type. When you connect from the Pega 7 Platform to external systems and services that require Kerberos authentication, the Pega 7 Platform stores the user Kerberos credentials and makes them available in Pega 7 Platform connectors.
For more information, see Using Kerberos credentials in a Pega application to authenticate and access external systems.
Text analytics infrastructure upgraded to Java version 1.7
Valid from Pega Version 7.2.2
The JAR libraries that support the text analytics features of the Pega 7 Platform have been upgraded to Java 1.7. As a result of the upgrade, you can validate the Ruta scripts that contain entity extraction models and view error reports if the imported Ruta scripts are invalid. This upgrade helps you to ensure that the structure of the entity extraction models that you import to your application is always correct.
For more information, see Text Analyzer.
Visual Business Director can be used in HIPAA-regulated environments
Valid from Pega Version 7.2.2
Communication between the Visual Business Director client nodes and the Visual Business Director server nodes now uses PRCluster. This new setup allows Visual Business Director to use the underlying clustering technology instead of depending on third-party solutions.
For more information, see Visual Business Director service.
New Decision Strategy Manager alerts
Valid from Pega Version 7.2.2
Autonomic Event Services (AES) is now monitoring new Decision Strategy Manager (DSM) alerts that allow diagnosis of performance-related issues with Decisioning services (Adaptive Decision Manager, Visual Business Director, Data Flow, and Decision Data Store).
For more information, see Performance alerts, security alerts, and AES and Services landing page.
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.