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.
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.
Conditional paths added to case life cycle
Valid from Pega Version 7.3.1
You can now add a conditional path to a process in the life cycle of a case. By defining the decisions that cause a process to follow different paths, you can create cases that support more than one outcome.
For more information about conditional paths, see Conditional paths in a case life cycle.
Receive and reply to push notifications for Pulse messages
Valid from Pega Version 7.3.1
You can now receive push notifications on your mobile device when another user references you in a Pulse message or likes your messages in a Pulse conversation. You can both receive and reply to the push notifications that you get when another user posts on your profile, adds messages to a Pulse conversation in which you are involved, or posts comments on a case that you are following. To receive push notifications, select mobile push as a notification channel when you configure your notification preferences.
For information about Pulse enhancements, see Pulse enhancements for social collaboration.
The Run Data Flow shape replaces the Run Interaction shape
Valid from Pega Version 7.3.1
The Run Interaction shape in flows has been replaced by the Run Data Flow shape to introduce a consistent way of making decisions and capturing responses. You can now run a single-case data flow by referencing the data flow in the Run Data Flow shape. The data flow must have an abstract input and abstract or dataset output.
For more information, see Running a decision strategy from a flow, About Data Flow rules and Interactions in flows are no longer supported by the Run Interaction shape.
Interactions in flows are no longer supported by the Run Interaction shape
Valid from Pega Version 7.3.1
The Run Interaction shape in flows has been replaced by the Run Data Flow shape, which supports running a single case data flow with a strategy. Flows that include the Run Interaction shape continue to work; however, you must now use the Utility shape to reference any new interactions that you create.
For more information, see Running a decision strategy from a flow and About Interaction rules.
Pulse gadget for feeds from multiple data sources
Valid from Pega Version 7.3.1
You can now use the pxFeed gadget to change the information that you want to display in a Pulse activity feed. By customizing the gadget, you can allow users to post messages on the activity feed and show messages from multiple data sources, for example, comments that are posted on a user's team feed.
For information about Pulse enhancements, see Pulse enhancements for social collaboration.