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.
Expose properties in Decision Data Store
Valid from Pega Version 7.3.1
You can now expose properties in Cassandra-based Decision Data Store data sets. With this solution, you can update single properties in extended customer analytic records (XCAR) without having to update the full customer record.
For more information, see XCAR in Decision Data Store.
Enhancements to bulk editing options for unversioned propositions
Valid from Pega Version 7.3.1
Bulk editing options for unversioned propositions have been enhanced to allow the use of Excel for editing. You can export and import unversioned propositions into Excel by using the Import wizard. Additionally, data types replace decision tables as the new storage format for unversioned propositions.
For more information, see Data type management and Proposition management enhancements.
Reuse existing propositions across applications
Valid from Pega Version 7.3.1
You can reuse existing propositions from built-on applications by using a new wizard to copy proposition groups across applications. This wizard gives you more options and flexibility when you define the business hierarchy in your application.
For more information, see Proposition management enhancements.
Migrate DDS data across various schema versions
Valid from Pega Version 7.3.1
You can use multiple versions of a single Decision Data Store (DDS) data set type in different applications that run on the same Pega® Platform instance and efficiently move data across those versions even if the underlying data schema is different. This solution improves the data management process and simplifies the reuse of existing data.
For more information, see Decision Data Store migration.
Support for PMML version 4.3 in predictive models
Valid from Pega Version 7.3.1
You can now leverage predictive models in the Predictive Model Markup Language (PMML) version 4.3 by importing them into predictive models on Pega® Platform. Pega Platform utilizes a large part of the PMML standard with the exception of some PMML 4.3 features that are not supported in the Predictive Model rule.
For more information, see Support for PMML version 4.3 in predictive models and Creating a predictive model.
Emit remaining event strategy data at the end of a data flow run
Valid from Pega Version 7.3.1
Data flows have been updated to prevent data loss in event strategies. By default, when a batch or a real-time data flow stops and it contains an event strategy with Tumbling windows, all of the events that are in the Tumbling windows are emitted. Event emission triggers further processing in the event strategy, like aggregations and joins.
For more information, see Enhancements to data flows that contain event strategies and Event Strategy rule form - Completing the Event Strategy tab.
New aggregation functions in event strategies
Valid from Pega Version 7.3.1
You can use new functions in event strategies to build standard and complex aggregations. With new aggregation functions you can detect additional patterns in streams of data and deliver actionable insights.
For more information, see Adding aggregations in event strategies.