Published Release Notes

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.

Import to and export from network storage

You can import development artifacts from and export development artifacts to network storage. Use the Import wizard, the Export wizard, or the service-enabled system management command-line tool for these activities.

For more information, see Tools for migrating rules and data.

Application import generates explicit DDL in IBM DB2 for z/OS

In IBM DB2 for z/OS databases, importing applications that include schema changes now generates explicit DDL. When a database administrator edits the DDL before applying the schema changes, they can create consistent object names across production levels and leverage naming standards for configuration and maintenance. If your application has a separate Data-Admin-DB-Name, you must configure import parameters.

For more information, see IBM DB2 for z/OS: Preparing to import an application with schema changes and a separate DB-Admin-DB-Name.

Improve application loading time with preflight optimization

Preflight optimization increases your application's initial display time by reducing unnecessary static content (JavaScript and Cascading Style Sheet files). To run the optimization process, click Designer Studio > User Interface > Application readiness > Preflight optimization.

For more information, see Preflight optimization.

Support for advanced text analysis when routing incoming emails

You can use text entity, category and sentiment analysis during the automatic routing of incoming emails. You provide text analysis of the text-based email content by defining routing rules, so that an automatic decision is made about how to process the received emails by the Pega^® Intelligent Virtual Assistant. You can route the email content to an operator, assign it to a work queue, or open a top-level case with the information.

For more information, see Configuring routing conditions for automatic email handling.

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.

Upgraded rich text editor

Content that you copy from a word processor or spreadsheet and paste into the upgraded rich text editor keeps its original formatting. You can paste text and tables into a Pega^® Platform application without losing formatting or styles.

For more information, see Rich text editor.

Encrypt sensitive case data by using a secure default Pega Platform cipher and AWS KMS keys

You can encrypt sensitive data within your application without having to write custom cipher classes. You can configure encryption on the Data Encryption landing page by using your own keys managed in your private Amazon Web Services Key Management Service (AWS KMS) instance. Pega^® Platform encryption uses keys that are stored in AWS KMS to support both time-based and on-demand key rotation. Technical issues can arise in some cases, for example, if a key is deleted from AWS KMS.

For more information, see Potential problems with keystores when using AWS KMS, Configuring a Platform cipher, Types of ciphers.