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.

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.

Unicode-enabled database for international language support

Valid from Pega Version 7.2.1

The Pega 7 Platform database has been enhanced to natively support Unicode multibyte character set encoding when using Postgres on Pega Cloud. This enhancement allows you to store data in languages such as Japanese, Chinese, and Korean.

Add custom HTTP response headers in your application

Valid from Pega Version 7.2.1

The Pega 7 Platform supports the addition of custom security HTTP headers that are supported by your browser. For example, you can now create custom X-Frame-Options, X-XSS-Protection, and Strict-Transport-Security headers. These headers improve the security of your application against client-based attacks.

For more information, see Creating a custom application header

Change the type of an existing field

Valid from Pega Version 7.2.1

You can now change the type of an existing field on the Data model tab of a case type or data type, resulting in a more efficient development process at design time. If there are any validation issues when changing a type, an error message is displayed, and the type cannot be modified by using this method.

For more information, see:

Open authoring for rule forms has been removed

Valid from Pega Version 7.2.1

Open authoring for rule forms has been removed. You can now edit decision tables and map values by using the application and supported browser of your choice; Microsoft ActiveX controls are no longer required. In addition, support for external XML, HTML, and Java IDE editors has been removed.

Pega Express application views simplify portal creation

Valid from Pega Version 7.2.1

Pega Express application views offer a simple, intuitive authoring experience for portals. Application view templates support responsive application development and offer mobile-specific templates. You can create portals by selecting from a predefined set of application view templates.

For more information, see Application views.

Rule form search

Valid from Pega Version 7.2.1

You can now search for content within some rule forms by clicking Search rule on the Actions menu. The search results and the tabs of the rule form that contain the search results are highlighted.

For example, you can find the properties that are used in a when condition inside an activity without navigating to each tab, when condition, transition, and method in the activity.

Delegate service-level agreements

Valid from Pega Version 7.2.1

You can now delegate service-level agreements (SLAs) to your business line by clicking Actions > Delegate. You can also delegate circumstanced versions of SLAs.

For more information about delegations, see Delegating a rule or data type.

Circumstance a rule by different properties

Valid from Pega Version 7.2.1

You can specialize or circumstance a rule by a different property even if the base rule is circumstanced by another property. This flexibility can help address cases where the same rule needs to be circumstanced by different properties. When you circumstance a rule by different properties, the circumstanced versions of the rule must be in different rulesets or Applies To classes.

You can circumstance a rule by a different property in the same ruleset, but in a higher version, by withdrawing the existing circumstanced versions.

For more information, see Circumstance a rule with different properties or templates.

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