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.

Access work items directly after login

Valid from Pega Version 7.2.1

You can now directly access work items that you receive as email notifications or URLs. The Pega 7 Platform opens the work item after successful user authentication instead of redirecting you to the portal. For a valid user, the type of authentication or number of failed login attempts does not affect this direct access.

For systems that use basic or secure basic authentication, administrators can disable the redirect URL by setting the authentication/basicschemes/redirectToLoginScreen switch to false.

Support for Hotfix Manager in service-enabled system management

Valid from Pega Version 7.2.1

You can manage hotfixes by using a REST service from Hotfix Manager in the service-enabled system management utility. With service-enabled system management, you can manage hotfixes simultaneously on more than one Pega 7 Platform system. You can manage the following hotfix operations: install, scan, commit, rollback, and GenerateDDL.

For more information, see Managing hotfixes (service-enabled).

Improved Pega 7 Platform upgrade and update time

Valid from Pega Version 7.2.1

The Pega 7 Platform upgrade and update tools have been improved to streamline indexing. Upgrading and updating are faster than with previous releases.

Option to resume failed upgrades and updates

Valid from Pega Version 7.2.1

When you upgrade or update to Pega 7.2.1, you can opt to have the system resume the deployment after a failure to avoid restarting the deployment and to save time. The deployment resumes at the point of failure and does not repeat any successful steps. This functionality is not supported for new installations. For more details, see the Pega 7 Platform Upgrade Guide and the Pega 7 Platform Update Guide.

Open access to quiesced servers when using immediate drain

Valid from Pega Version 7.2.1

When using the immediate drain method to perform quiesce on a node, any operator can now access a quiesced server for root cause analysis or remediation, regardless of their user role or privileges. For quiesced server access when using the slow drain method, you must still include either the PegaRULES:HighAvailabilityAdministrator or PegaRULES:HighAvailabilityQuiesceInvestigator user role in a user's access group. Administrators using the slow drain method without either of these user roles are exiled from the quiesced node and are redirected to an active node.

For more information, see Immediate drain available for quiesce when using high availability.

New passivation and activation activities

Valid from Pega Version 7.2.1

Two new activities have been implemented, pyPrePassivation and pyPostActivation, which are run every time operator passivation occurs, regardless of the node quiesce state. These activities save and restore the requestor state during passivation and activation. In order for the pyPrePassivation or pyPostActivation activity to be run as expected, you must implement the activity by using the correct Applies To class (@baseclass).

The previous activities that were run during the quiesce process, pyPreQuiescePassivation and pyPostQuiesceActivation, have been deprecated.

For more information, see the Pega 7.2.1 High Availability Administration Guide.

Transition effects for actions in custom mobile apps

Valid from Pega Version 7.2.1

Custom mobile apps that are developed on the Pega 7 Platform can include built-in transition effects that animate your forward or backward movement in cases that use flows. This feature adds to the look-and-feel experience of the custom mobile app.

You can also manually add a transition effect to actions that do not support built-in effects by using the Run Script action and calling the pega.desktop.setNativeTransition() JavaScript method.

For more information, see Transition effects on actions.

Design templates in Pega Express

Valid from Pega Version 7.2.1

You can now use design templates to control the layout of form fields in Pega Express. Use the form builder Layouts tab to select a layout for the form and organize the fields in the layout regions.

For more information, see Adding a design template to a form in Pega Express.

Support for reserved keywords in database column names

Valid from Pega Version 7.2.1

Databases use reserved keywords such as Group, Order, Rank, and Date to define and manipulate data. The list of reserved keywords is specific to each database. Column names can now include reserved keywords.

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.

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