Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Specify the scope for rolling back rules and data to a restore point

Valid from Pega Version 8.4

Create restore points to save the state of all rules and data in your system at a significant point in time, for example, before you import an application. Roll back to that restore point to return the system to that state. Now, you can filter which rule and data instances are returned to their previous state:

  • System: Roll back every rule and data instance that has a history record.
  • User: Roll back rule and data instances modified by a specific user. If any rule was changed by more than one user, you will see an error message and must use the system rollback.
  • Application: Roll back rule and data instances in a specific application.

For more information, see Using restore points to enable error recovery.

Client-server deployment of Hazelcast

Valid from Pega Version 8.4

Pega Platform now supports the client-server model for the Hazelcast service, which provides cluster communication and distributes Pega Platform features across nodes. This optional deployment model introduces independent scalability for both servers and clients in Pega Platform, improving stability for deployments that use a large number of nodes.

The Hazelcast client-server model is intended for select environments running Pega Platform 8.4 across a large number of nodes and should be deployed only when directed by Global Client Support.

Improved indexing performance by gradual retrieval of data

Valid from Pega Version 8.4

Search functionality in Pega Platform™ versions from 8.4.5 to 8.6 now includes the option to improve indexing performance when reading query results from a large table in a database. For example, to load the recommended 50 records at a time, in the Pega-SearchEngine ruleset, create the indexing/distributed/fetchsize dynamic system setting, and set the value to 50.


Creating the fetchsize dynamic system setting ensures that your system does not crash while indexing classes with numerous instances.

For more information, see Creating a dynamic system setting.

Supported JDBC drivers

Valid from Pega Version 7.1.1

Pega 7.1.1 supports Java 6 and Java 7 SDKs only. Ensure that the JDBC driver you are using supports those versions of Java. See your database installation or upgrade documentation for additional information.

DatabaseJava 6Java 7
Oracleojdbc6.jarojdbc7.jar
MSQLsqljdbc4.jarsqljdbc4.jar
DB2 LUWdb2jcc4.jardb2jcc4.jar
DB2 z/OS*db2jcc4.jar or jdb2jcc.jar**db2jcc4.jar
PostgreSQLpostgresql-9.1-903.jdbc4.jar***postgresql-9.1-903.jdbc4.jar

* JDBC drivers are only available from the DB2 for z/OS product. Additionally, you need db2jcc_license_cisuz.jar in the same directory as db2jcc4.jar.

** The db2jcc.jar has been deprecated and may not be supported in future releases.

*** This .jar file is required for PostgreSQL version 9.1.x.

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.

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.

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.

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:

For more information about alerts, see Performance alerts, security alerts, and Autonomic Event Services.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us