Support for Apache Cassandra
Valid from Pega Version 7.3.1
The Pega® Platform can now read data from and write data to an Apache Cassandra database. Apache Cassandra is a NoSQL database that you can use when a NoSQL database better meets your scalability and processing requirements.
For a list of supported and unsupported features, see Apache Cassandra support.
Requestor pools management in Designer Studio
Valid from Pega Version 7.3.1
On the new Requestor Pools landing page, you can view and manage requestor pools across the cluster, including on the current node and remote nodes. By using this landing page, you can tune the requestor pools to improve the performance of services. You can clear the requestor pool for a service package and view the requestor pool basic metrics and configured thresholds.
For more information, see Requestor pools management, Clearing a requestor pool, Viewing details for a requestor pool, Tuning a requestor pool configuration.
Class structure expanded for surveys and questions
Valid from Pega Version 7.3.1
You can now create surveys and questions at any class level. Because there is no longer a restriction on which class of flows can use the Survey and Question smart shapes, you can create more contextual surveys that reference embedded properties, or instances of classes, that you define outside the Work- class structure.
For more information about using the Survey or Question smart shapes in a flow, see Integration methods for surveys.
Locatable pages are deprecated
Valid from Pega Version 7.3.1
Locatable pages are deprecated. Use a data page instead. Data pages provide improved performance. When you save a rule that has a Locate Page Activity or when you create an activity of type Locate page, a guardrail warning is displayed indicating that this feature has been deprecated.
For information about data pages, see Data pages.
Module version report generated from Designer Studio
Valid from Pega Version 7.3.1
From the new Class Management landing page, you can generate the module version report that provides information about classes in your system, module versions, and version creation dates. You can generate the report for all the nodes in the cluster or for a selected node that is either current or remote. The report is useful for debugging system problems because it helps identify the module version that is causing problems on a specific node.
For more information, see Module version report.
Like and bookmark Pulse messages
Valid from Pega Version 7.3.1
You can now like messages that are posted to Pulse and view the number of likes for each message. You can also bookmark the messages that you want to view in your activity feed.
For information about Pulse enhancements, see:
- Pega Express 7.3.1 – Communicating with Pulse
- Pega Platform 7.3.1 – Pulse enhancements for social collaboration
Real-time updates in Pulse
Valid from Pega Version 7.3.1
You can now view real-time updates of messages in Pulse. If a user posts a comment on a Pulse conversation while you are viewing the conversation, you receive a notification in real time, which you can click to refresh the conversation and see the comment.
For information about Pulse enhancements, see:
- Pega Express 7.3.1 – Communicating with Pulse
- Pega Platform 7.3.1 – Pulse enhancements for social collaboration
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.