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.

Enabling security policies now requires current password

Valid from Pega Version 7.1.3

As part of Pega’s initiative to protect against malicious attacks, the change password dialog has been enhanced.  When Security Policies have been enabled for your system, new users or those with expired passwords will now be prompted for both their existing password as well as their desired new password.

For more details, review the Designer Studio > System > Settings > Security Policies landing page.

Real-time pulse processing for multinode systems

Valid from Pega Version 7.1.9

Multinode development environments now use real-time pulse processing. Previously, when a change was made on one node, the pulse processing interval could take a minute or more for that change to be reflected on another node. Now, when a rule is changed on one node, that change is immediately reflected on all the other nodes in the cluster. This change helps to ensure that users are running a rule on the same node as where the rule was changed.

Verifying that a Pega 7 Platform instance is running

Valid from Pega Version 7.1.9

You can verify whether a Pega 7 Platform instance is up and running by entering this URL: http://<<hostName:port/contextName>>/PRRestService/monitor/pingservice/ping

The Pega 7 Platform Engine responds with HTTP Response Code 200 if the instance is available. The response contains JSON text in the format { "duration":"<time in milliseconds>" }. Any other response codes or timeout indicate that the instance is unavailable.

Database storage used for passivation in High Availability mode

Valid from Pega Version 7.1.9

When an application is running in High Availability mode, the value attribute for initialization/​persistrequestor/storage in the prconfig.xml file or the Dynamic System Settings​ now defaults to "database."

Previously, applications running in High Availability mode required shared passivation, where either initialization/​persistrequestor/storage was set to “OnTimeout” or a custom passivation mechanism was used. The change to using database by default provides persistent storage for passivation, and provides control for the landing page for High Availability.

For more information, see Understanding passivation and requestor timeouts and the High Availability Administration Guide.

New field types in Form Builder

Valid from Pega Version 7.1.9

You can create forms in Form Builder that include the following field types:

  • Data reference – Prompts users with a list of data records or instances of a specific data type.
  • User reference – Prompts users to select or search for an existing user in the application.

For more information, see Data references in Form Builder and User references in Form Builder.

Reusable components in Form Builder

Valid from Pega Version 7.1.9

You can reuse an existing form or data reference when creating a form. By referencing the existing fields in your application, you save time and build forms that are easier to maintain. Refer to the Reuse fields panel in Form Builder to view all of the fields, forms, and data references in your application.

For more information, see Reuse fields panel in Form Builder.

Support for enterprise and express applications

Valid from Pega Version 7.1.9

When you run the New Application wizard, you can create two types of applications:

  • Enterprise – A full-scale application that has access to all the capabilities in the Pega 7 Platform.

    By default, enterprise applications are developed in Designer Studio, but users have access to express mode.
  • Express – A small-scale application that has access to a subset of the capabilities in the Pega 7 Platform.

    Express applications are developed in express mode, and are ideal for new users or for quickly testing functionality.

For more information, see Express applications.

Pega 7 Express is available on-premises

Valid from Pega Version 7.1.9

You can now experience Pega 7 Express by switching your enterprise application from Designer Studio to express mode. By default, users with access to the Developer portal can switch between these two development environments. You can also create an express application to work in express mode exclusively.

Trial versions of Pega 7 Express continue to be available on the cloud. To view the documentation for both the cloud and on-premises environments, see Getting started with Pega 7 Express.

Access to Pega 7 Express from within Designer Studio is not supported on mobile devices.

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