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.

Access Manager portal

Valid from Pega Version 7.1.5

Changes to the Access Manager simplify the process of modifying the access rights of features for an application. The changes, including creation of an Access Manager portal, make it easier for non-technical users, such as business architects, to set access rights even if they may not have a deep understanding of Pega 7's security model and class inheritance structure.​

Support for large reference data in offline mobile apps

Valid from Pega Version 7.2

A data page in a Pega 7 Platform mobile application with offline capability enabled can now be marked as a large data page. This feature improves performance significantly when you have a large amount of data in which only individual records change.

In this situation, after the initial sync to the mobile app, only the changes in the large data page are synced instead of the entire large data page. The database table is created for such large data pages in the encrypted SQLite database on the device. Changes such as add, delete, or update are reconciled as row-level updates. Furthermore, you can use JavaScript to query against this data. A large referenced data page is supported by list-based components such as repeating dynamic layout, auto-complete, a dropdown list, and radio button.

Support for offline and online cases in a single mobile app

Valid from Pega Version 7.2

A single offline-enabled application can now support both the creation and processing of online-only and offline-ready cases.

For online-only cases, a list of both the offline and online cases is always available. Case assignment and processing is performed on the server so that a case is available only when the device is connected to the Internet or to data. When a connection is not available for processing an online-only case, an error message is displayed.

For offline-ready cases, a user can open an assignment and perform tasks on that case. There is also an option to explicitly display a harness from a server instead of a client store.

Offline mobility improvements

Valid from Pega Version 7.2

Several offline mobility improvements have been made in this release. Additional use cases have been added for configuring offline-enabled mobile apps at design time. Read-only grids with limited features are now supported offline. You can configure auto-populated properties, and you can create work with parameters. It is also possible to open work by handle. You can use decision shapes with Boolean expressions (no when rules) in screen flows. Barcode scanning is now available in offline mode.

Mobile user interface updates

Valid from Pega Version 7.2

Several improvements have been made to the mobile-related user interface of the Pega 7 Platform. The content of the Mobile tab on the Application rule form has been redesigned. The Offline Configuration and Mobile Certificates landing pages are now available. The Signature Capture control has improved. Post-processing can now occur after the signature has been captured. You can auto-submit with the form submit. You can apply the signature to a page instead of applying it as an attachment to the case. The clear action completely removes the signature from the work object, keeping only the latest iteration of the signature. Touch interactions have been significantly improved. Response time is faster and there is better feedback on the touch action.

Support for OAuth 2.0 authorization code grant type

Valid from Pega Version 8.1

Pega Platform™ now supports the OAuth 2.0 authorization code grant type, which allows Pega Platform to act as an OAuth 2.0 access token provider for native applications on mobile and other devices. By using the authorization code grant type for mobile clients, you no longer need to implement a variety of standards for various authentication providers. The authorization code grant type also supports the Proof Key for Code Exchange standard (PKCE) for securing public clients.

For more information, see Creating and configuring an OAuth 2.0 client registration.

Use client-based access control to support EU GDPR requirements

Valid from Pega Version 8.1

You can use client-based access control (CBAC) to satisfy the data privacy requirements of the European Union General Data Protection Regulation (GDPR) and similar regulations. By using client-based access control, you can identify the personal data of clients and automatically process requests to view, update, or remove the data in a secure manner. You can also enforce restrictions on the use of this data in application functions.

For more information, see Client-based access control.

Support for multiple custom mobile apps for a Pega Platform application

Valid from Pega Version 8.1

To enhance the user experience and provide support for native mobile components, you can create multiple custom mobile apps for a Pega Platform™ application. For each custom mobile app, you must create a different mobile channel interface. In addition, you can configure each custom mobile app to run only in a specific portal for an application. The custom mobile app uses this portal regardless of which default portal is defined for the access group.

For more information, see Selecting a portal for a custom mobile app.

Changes in large data page support in offline-enabled custom mobile apps

Valid from Pega Version 8.1

You can now create offline-enabled custom mobile apps that store reference data in large data pages that are sourced from report definitions, even if these report definitions return no records. Synchronization of these custom mobile apps does not fail. Also, you can now use page type properties as large data page properties.

For more information, see Creating and sourcing large data pages to store large reference data in offline-enabled applications and Custom populator JavaScript functions for large data pages.

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