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.
Apply logic to data import fields
Valid from Pega Version 7.3.1
When importing data from an external system, you can translate data fields into values that can be read by Pega® Platform. From the Import wizard, you can do the following actions:
- Apply a decision tree or decision table to the data that is imported for a field.
- Use imported data for a field to look up a value in another record. For example, you can look up the key of a record that uses an external identifier to populate a foreign key field.
- Create templates that contain business logic, which eliminates the need to handle data transformations manually during preprocessing.
For more information, see Transforming data during import.
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.
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.
Ability to map JSON to clipboard properties by using a data transform
Valid from Pega Version 7.3.1
You can now map the entire JSON file or individual properties to and from the clipboard by using a data transform. Using a data transform makes it faster and easier to connect your Pega® Platform to your system of record.
For more information, see Data transforms.
Rules Assembly cache is deprecated
Valid from Pega Version 7.3.1
Rules Assembly (RA) cache and custom settings for its corresponding fua/assemblyCacheMode
prconfig.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.
Data validation before importing
Valid from Pega Version 7.3.1
Data imported into a data type is now validated before it is imported. Validating data before importing it ensures that the data is valid and reduces the amount of time required to manually analyze and validate your data.
For more information about importing data into a data type, see Importing data for a data type.
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.