Published Release Notes

Continue batch data flow runs that failed and reprocess partitions with the failed records

You can now continue batch data flow runs that failed and complete them with failures. You can also identify all the records that failed during a batch data flow run that is completed with failures. After you fix all the issues that are related to the failed records, you can reprocess the failures by resubmitting the partitions that contain the failed records. This option saves time when your data flow run processes millions of records and you do not want to start the run from the beginning.

For more information, see Data flow run updates.

Multi-Select list control

You can add a Multi-Select list control to a user form so that application users can select more than one value for a single field. These lists save time and ensure accuracy by supplying a list of valid values for an input field. You can source a Multi-Select list control from a data page, clipboard page, or report definition.

For more information, see Adding and configuring a Multi-Select list control.

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.

Improved usability for feature management

You can now manage your features more effectively by implementing the following changes in your application:

• Move features to different levels to change the structure of your feature hierarchy.
• Provide descriptions that are longer than 256 characters to improve the readability of features.
• Quickly remove irrelevant features without having to manage dependencies on built-on applications or previous application versions.
• Consolidate features into one application layer when you are ready to ship your application.

For more information about feature management, see Managing the features in your application.

Real-time statistics added to application overviews

You can now use the Application Overview landing page to get information about the number, type, and status of work items that are associated with your features. By referring to the statistics and progress bars that update as your team creates and resolves work items, you can track feature development in real time without interrupting your development team for status updates.

For more information, see Real-time statistics for feature development.

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.