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.

Use multiple built-on applications to enhance ruleset reuse

Valid from Pega Version 7.2

Applications can now have multiple built-on applications, allowing rules to be reused as a part of a built-on application at run time while being developed independently at design time.

Previously, applications built in Pega 7.1 and earlier versions were assembled in a single linear application stack--one application built on top of another application, and so on. Attempting to reuse rulesets and frameworks across applications resulted in having to splice applications together, creating challenges when attempting to support the use of these custom created applications. Starting in Pega 7.2, applications are built on to other applications by using a hierarchical tree structure, and the Pega 7 Platform automatically converts this tree into a linear application stack.

For more information, see Using multiple built-on applications and the Ruleset behavior at design time section in Application stack hierarchy for multiple built-on applications.

Stage-based revision and change request management enhancements

Valid from Pega Version 7.2

The revision and change request processes are based on the case management capabilities provided by the Pega 7 Platform. The customizable flows that controlled the behavior of the revision and change request management (pyManageRevision, pyManageChangeSet, pyApproveChangeSet, and pyDirectDeployment) are now part of the Revision and Change Request case types that govern the behavior of revision management. The change from flow-based to stage-based revision management makes the process more transparent and easier to modify.

For more information, see Stage-based revision and change request management.

Support for delegating map values, correspondence rules, and circumstances

Valid from Pega Version 7.2

You can now delegate map values and correspondence rules from the Actions > Delegate menu. In addition, you can delegate circumstanced types of the following supported rules and data types:

  • Map values
  • Correspondence rules
  • Paragraphs
  • Decision tables
  • Data types

Help now available for the Predictive Analytics Director (PAD) portal

Valid from Pega Version 7.2

Help topics for Predictive Analytics Director (PAD) are now available. The comprehensive PAD documentation helps you to understand how to develop and create predictive models that you can combine with other components in Decision Strategy Manager (DSM).

For more information, see Predictive Analytics Director (PAD) and Improvements to the Predictive Analytics Director (PAD) portal.

Offline support for mobile applications

Valid from Pega Version 7.2

You can work on assignments and create cases while your mobile device is offline. By enabling offline support for a case type, you can move cases closer to resolution while your application is disconnected from the network.

For more information, see Enabling offline for support for a case type.

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.

Relevant records to define reusable assets

Valid from Pega Version 7.2

Relevant records describe the collection of rules that refine the behavior, presentation, and definition of a case or data type. They are commonly used to designate records from an inherited class as important or reusable in a child class.

Use relevant records to define information displayed in certain Pega 7 Platform application screens and fields. The Pega 7 Platform provides a number of items marked as relevant records, and you can further manage relevant records for your own case and data types.

For more information, see Relevant records.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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