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.

CyberArk password vault support added for Pega database

Valid from Pega Version 8.3

With the CyberArk password vault, you can store your systems' passwords in a secure, central location and retrieve them from that location instead of directly entering credentials into the systems. This support is available only for IBM WebSphere environments.

For more information, see Pega Platform deployment guides.

Support added for multiple mashups

Valid from Pega Version 8.3

You can now include multiple mashups on a single webpage or browser, even if the mashups have different application and authentication requirements. Use mashups to embed a Pega Platform™ application as a gadget on your website. For example, you can embed Web Chatbot and Self-Service Advisor on the same website.

For more information about mashups, see Configuring the Mashup channel.

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.

Identify, install, and manage hotfixes with the Hotfix Manager

Valid from Pega Version 7.1.8

Hotfixes are packages of files that address issues in Pega 7 and in participating Industry Applications. With Hotfix Manager, you can:

  • Scan your system for installed and missing critical hotfixes and create a report that you can provide to Pegasystems Support for diagnostic purposes.
  • Review the descriptions and contents of hotfixes.
  • Install, rollback, and commit hotfixes.
  • Manage hotfixes that include schema changes or require other special handling.

The Hotfix Manager replaces the Update Manager Hotfix Installer and System Scanner, both of which are deprecated. For more information, see Hotfix Manager identifies, installs, and manages hotfixes to Pega 7 and participating Industry Applications.

Enhanced product rule form for easy application packaging

Valid from Pega Version 7.1.8

The enhanced product rule form allows you to add applications in Delta mode, which includes only the patch version of the rulesets that comprise the application rule. You can also use Global exclusions to exclude one or more rules that are not associated with a ruleset version.

These enhancements allow easy packaging of non-versioned rules that are often deployed separately and reduce the need to manually add them later.

For more information, see Product rules - Completing the Contents tab.

Updated Rule-Utility-Function resolution

Valid from Pega Version 7.1.8

Rule-Utility-Function rules are now resolved based on ruleset.

Previously, if you had the same function @xyz() in different libraries in different rulesets, you could not call the function by using @xyz, because that would throw an exception.

The resolution process has since been updated so that rule resolution is now based on the highest ruleset in context. This update makes the function resolution process consistent with how rule resolution is performed for other rule types.

For more information, see Functions in expressions.

Define function input parameters on the Create or Save As forms

Valid from Pega Version 7.1.8

When creating or updating a Rule-Utility-Function ruleset in Designer Studio, use the Create or Save As forms to define or change parameters as a part of the form. The Parameters section on either of these forms allows you to set the function's name and Java type before opening the function.

Previously, you updated these fields on the Parameters tab for the function after the form was created. Moving these fields to the Create and Save As forms helps to proactively detect functions with the same signature in the same ruleset before saving the function.

For more information, see Defining function input parameters on the Create or Save As forms.

Support for Oracle TIMESTAMP data types

Valid from Pega Version 7.1.8

The Oracle TIMESTAMP data type is now fully supported throughout the Pega 7 data layer. The TIMESTAMP columns for data provide greater precision than the previously available DATE columns.

This release does not include any columns that use the TIMESTAMP data type at installation. However, after installation or upgrade:

  • Any newly created columns (for example, those created when optimizing a property or defining a new table) use the TIMESTAMP column type.
  • Any existing data still uses DATE values.
    • Oracle users can manually convert any existing DATE column types to use a TIMESTAMP column type instead.
    • Altering the column type for existing values in a column does not provide any greater precision for those values because they still use DATE values and not DATETIME values.

For more information, see DateTime property mapping in Oracle for Pega 7.

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