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.
Pega Cloud Services support for the AWS EU (London) and US East (Ohio) regions
Pega Cloud Services now supports deployment to the Amazon Web Services (AWS) EU (London) and US East (Ohio) regions. Deployment across multiple availability zones within a geographical region protects against zone faults and localized service disruptions, and ensures high availability.
For more information about regions and availability zones, see Pega Cloud Services capabilities.
.
These additional regions are available as of QIV 2017.
Continue batch data flow runs that failed and reprocess partitions with the failed records
Valid from Pega Version 7.3.1
You can now continue batch data flow runs that failed and complete them with failures. You can also identify all the records that failed during a batch data flow run that is completed with failures. After you fix all the issues that are related to the failed records, you can reprocess the failures by resubmitting the partitions that contain the failed records. This option saves time when your data flow run processes millions of records and you do not want to start the run from the beginning.
For more information, see Data flow run updates.
Rules Assembly cache is deprecated
Valid from Pega Version 7.3.1
Rules Assembly (RA) cache and custom settings for its corresponding fua/assemblyCacheModeprconfig.xml file setting are deprecated because they are obsolete. A warning is logged at startup if a custom (non-default) value is specified for fua/assemblyCacheMode in the prconfig.xml file. The functional behavior of the system is not affected.
Improved Clipboard performance
Valid from Pega Version 7.3.1
Clipboard performance has been enhanced to use high-speed, read-only data pages, making processing faster. For some high throughput use cases, performance might be degraded. If performance is degraded, you can use a restricted feature set for a specific read-only data page by selecting Restricted feature set for high throughput on the Load management tab of the data page rule.
For information about unsupported features when using a restricted feature set, see High-speed data page support.
Simplified deployment of stand-alone Apache Ignite servers
Valid from Pega Version 7.3.1
You can now install or upgrade Pega® Platform in client-server mode, which uses Apache Ignite in a simplified way. The new installation process for stand-alone Apache Ignite servers does not require that you provide database credentials in a text file to communicate with Pega Platform nodes (clients). You provide this information by using JNDI support instead.
For more information, see Apache Ignite client-server clustering topology and the appropriate Deployment Guide.
New alerts for the Apache Ignite cluster
Valid from Pega Version 7.3.1
New Pega® Platform alerts identify issues with Apache Ignite cluster members (nodes) that operate either in client mode or server mode. Refer to these alerts to diagnose problems with the Apache Ignite cluster and to protect against hard-drive failures or loss of data.
The new alerts are:
- PEGA0088: Client node unexpectedly disconnected from the cluster
- PEGA0089: A node left the cluster
- PEGA0090: Cluster segmentation causes subclusters to form
- PEGA0091: Data stored in one or more cluster caches is lost
- PEGA0092: Number of servers in the cluster falls below the recommended settings
For more information about alerts, see Performance alerts, security alerts, and Autonomic Event Services.
Decision Data Store and HDFS data set types become resumable
Valid from Pega Version 7.3.1
Decision Data Store (DDS) and HDFS data set have been enhanced to be resumable. As a result, data flow runs that reference Decision Data Store or HDFS data sets as their primary data source are now resumable. You can pause and resume such data flow runs.
For more information, see the Resumability of data flow runs section in Data flow run updates.
Integrate the intelligent interaction activity for text analytics into your application
Valid from Pega Version 7.3.1
Employ text analytics and machine-learning capabilities in multichannel applications by integrating the pyRunInteraction activity for content parsing and analysis. By calling this activity, you can automatically analyze any incoming text data, such as instant messages, posts, emails, and so on, to detect sentiments, categories, entities, or intents that can help you with automatic case creation and routing. For example, you can use this activity to populate case properties based on detected entities such as customer name, email address, and account number.
For more information, see Intelligent interaction in text analytics.