Tracing Cassandra queries in a Decision Data Store data set
Valid from Pega Version 7.3
You can now enable the Trace option for every operation in the Decision Data Store data set to collect information about how the Decision Data Store queries are executed in Cassandra. You can view this information in the clipboard and use it to troubleshoot and optimize performance of the Decision Data Store data sets and Decision Data Store nodes. All the queries and related events are collected on the DDSTraces page on the same Pega thread.
For more information, see Tracing Decision Data Store operations.
Enhanced functionality of the Decision Manager portal
Valid from Pega Version 7.3
The Decision Manager portal now provides more revision management options. The Decision Analytics work area for development of predictive, adaptive, and text analytics models is now part of the Decision Manager portal. PegaUnit testing of rules is more convenient from a new Automated Testing landing page. Revision managers can reassign change requests back to strategy designers or other users of the Decision Manager portal without losing changes that were already made.
For more information, see Enhancements to the Decision Manager portal.
Use Kafka data sets in Pega Decision Strategy Manager
Valid from Pega Version 7.3
You can create Kafka data set rules to connect to an external Apache Kafka server cluster and use this data set in decision management for processing real-time streaming data. Integrating Kafka data sets into complex event processing (CEP) as part of Event Strategy rules provides a fault-tolerant and scalable solution for processing real-time data feeds.
For more information, see Kafka data sets in decision management.
Send event notifications in Pega Platform
Valid from Pega Version 7.3
You can configure applications to notify users of case changes or other significant events that occur in an application. Use notifications to engage application users by providing key updates that might be of interest to them.
You can deliver notifications over the default web gadget and email channels or use a custom channel that you created. You can configure multiple web gadgets to display different kinds of notifications. The email channel supports notification frequency of instant, daily, or weekly.
Application users can set their own notification preferences in the run-time portals or override the set preferences for a specific case type instance.
For more information, see Sending event notifications and Management of user notification preferences.
Use definition classes to create Decision Data rules that contain text analytics records
Valid from Pega Version 7.3
Use the dedicated definition classes to create Decision Data rules that contain all the types of records that are used in text analytics, such as taxonomies, lexicon, entity extraction rules, and so on. By using these definition classes, you can quickly create, update, and manage the text analytics records in your application.
For more information, see Definition class of text analytics Decision Data rules.
Create resilient data flow runs
Valid from Pega Version 7.3
The resilience of data flow runs has been improved. If Data Flow service nodes fail, active data flow runs continue on the remaining functional nodes. Depending on the type of primary data source and the selected run failure policy, data partitions on the failed nodes can be reprocessed on another functional node or the data flow run is marked as failed for further investigation. You can also add or remove nodes from the Data Flow service while data flow runs are in progress. The runs are automatically rescaled.
For more information, see Data flow run updates.
Multiple notifications are delivered for the same Pulse post
Valid from Pega Version 7.3
When a user posts a Pulse comment, the users who subscribe to the activity feed might receive more than one notification if the posted comment triggers several notification rules.
For example, when a user posts a comment on a case that he or she follows, any response to the comment can result in the following notifications:
- Notification when a new comment is posted on the followed case (triggers the pyAddPulsePost notification definition)
- Notification when a comment is a response to the user’s original post (triggers the pyAddPulsePost notification definition)
- Notification when the user is mentioned in the comment (triggers the pyAddUserMentionedPost notification definition)
Pulse Extension points are deprecated
Valid from Pega Version 7.3
Beginning with Pega® Platform 7.3, Pulse uses the notifications feature to send notifications. As a result, Pulse extension points for email body, subject, and recipient list have been deprecated. Preferences set for Pulse notifications in earlier versions are no longer valid.
Use the alternatives listed in the following table to configure your Pulse message and notification preferences.
| Deprecated extension point | Alternative extension point | Corresponding notification rule |
|---|---|---|
| pyInstantPulseNotification (Correspondence) | pyAddPulsePost (Correspondence) | pyAddPulsePost |
| pyReplyPulseNotification (Correspondence) | pyAddPulsePost (Correspondence) | pyAddPulsePost |
| pyMentionsPulseNotification (Correspondence) | pyAddUserMentionedPost (Correspondence) | pyAddUserMentionedPost |
| pyMentionsInNonCaseContext (Correspondence) | pyAddUserMentionedPost (Correspondence) | pyAddUserMentionedPost |
| pyNewPulsePostSubject (Field Value) | pyAddPulsePostEmailSubject (Field Value) | pyAddPulsePost |
| pyNewPulseFilePostSubject (Field Value) | pyAddPulsePostEmailSubject (Field Value) | pyAddPulsePost |
| pyNewPulseReplySubject (Field Value) | pyAddPulsePostEmailSubject (Field Value) | pyAddPulsePost |
| pyMentionedUserSubject (Field Value) | pyAddUserMentionedPostEmailSubject (Field Value) | pyAddUserMentionedPost |
| pyMentionedFollowerSubject (Field Value) | pyAddUserMentionedPostEmailSubject (Field Value) | pyAddUserMentionedPost |
| pyMentionedFollowerWithFilePostSubject (Field Value) | pyAddUserMentionedPostEmailSubject (Field Value) | pyAddUserMentionedPost |
| pyGetListOfEmailReceivers (Activity) | D_pxGetCaseFollowers (Data page) | pyAddPulsePost |
To continue using the deprecated extension points, override the pyInvokepxNotify when rule and set it to return false.
For more information, see Management of user notification preferences.
Define partitioning of stream data sets
Valid from Pega Version 7.3
You can define partition keys for Data Set rules of type Stream to group similar properties and to process Data Flow rules that contain stream data sets more efficiently across multiple Data flow service nodes. Use this feature only for testing in non-production application environments.
New delivery method for Pega Survey
Valid from Pega Version 7.3
The functionality of Pega Survey is now provided by a standard ruleset in the Pega® Platform. This new delivery method keeps your survey capabilities in sync with the latest features and speeds up development because you no longer need to install or maintain a separate archive.
You must purchase a separate license to use survey capabilities in your application.
For more information about surveys, see the Pega Survey product page.