Published Release Notes

Module version report generated from Designer Studio

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

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.

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

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

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

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

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

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.

Enable different REST service rules for distinct resource URIs

You can now specify different service REST rules for distinct resource URIs. This functionality provides different processing options, request handling, and response handling for each distinct resource URI. Additionally, it eliminates the need to develop and maintain complex logic to handle all possible resource URI paths.

For more information, see Distinct URI specification for service REST rules.

Enable email notifications on agent failure

You can now get email notifications each time an agent fails with a PEGA0010 alert. By receiving notifications on agent failure, you can immediately take action to restart or fix the agent. You can enable email notifications on the Agent Management landing page.

For more information, see Enabling notification on agent failure and PEGA0010 alert: Agent processing disabled.