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.
Naming pattern changed for file data sets
Valid from Pega Version 8.6.3
File data sets are used to import from and export data to a file repository. In case of data export, prior to version 8.6.3, the first file exported had the same file name that was provided by the user in the data set, and any subsequent file exported to the repository had a unique identifier appended to it. Starting in Pega Platform version 8.6.3, each file has a unique identifier, automatically generated based on the data flow node, thread ID, and timestamp.
Upgrade impact
If your process to consume output files expects files with a specific name, it may not be able to process the resulting files correctly.
What steps are required to update the application to be compatible with this change?
If you have configured the process before updating to Pega Platform version 8.6.3, but the exported files are no longer recognized by downstream processing logic after the upgrade, ensure that the downstream tool is configured to recognize the files by a pattern rather than the full name. For example, when referring to files exported to the repository, use the * character to indicate a pattern instead of using the full file name. For example, use Export*.csv to refer to the files.