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.

Sign and encrypt signatures and content with additional algorithms

Valid from Pega Version 8.4

You can now authenticate using JSON Web Token (JWT) token profiles to symmetrically and asymmetrically encrypt both signatures and content. All algorithms in the Nimbus JWT library are supported, including nested tokens. Custom key identifier headers (kid) are also supported. Use token profiles to securely propagate identities and transfer data between systems.

For more information, see Creating a processing JSON Web token profile.

For more information, see Creating a generation JSON Web token profile.

Improved mobile app user experience

Valid from Pega Version 8.4

Pega Platform™ can now produce a better mobile experience through performance gains and flexible access settings. Apps now support quick-loading native worklists, smooth scrolling and swiping, and query-based search, which improve productivity for mobile users. In addition, you can make your app available to users without authentication, and enhance usability for products that do not require strict security controls.

For more information, see Securing mobile apps.

More efficient mobile development

Valid from Pega Version 8.4

The work environment for mobile app developers in Pega Platform™ is now more intuitive. Because every new out-of-the-box application now comes with a preconfigured mobile channel, you can start building mobile apps straight away. Create a mobile channel from scratch, and then customize it to include specific requirements for your new app.

The following updates enhance the process of building mobile apps:

  • Your application stores all mobile channels as rules. You can reuse these channels across all versions of your mobile apps for more convenient updates.
  • You can now configure contextual search from the mobile channel.
  • You can now create native mobile list pages for the app navigation directly from the mobile channel.
  • You can now add pages from web portals to a mobile app navigation pane, with full support for native mobile features, such as floating action buttons.
  • Mobile channels now support configuration through predefined templates, widgets, and actions.
  • You can now instantly preview your mobile channel configuration to see how the app displays on mobile devices.
  • Configuration of offline support for mobile apps is now available from a single, low-code page.
  • The preview section now offers a low-code pane, from which you can instantly start building a mobile app.
  • The mobile channel now supports adding custom iOS and Android modules.
  • Admin Studio now supports a mobile page, from which you can provide your own Mobile Build Server credentials and decide whether users need to provide authentication to download your mobile app.

Expanded checks for Java injection vulnerabilities (8.4)

Valid from Pega Version 8.4

The Java injection vulnerability check feature has been enhanced in Pega Platform™ to further prevent Java injection, including Edit validate, Edit input, and JSP rules. Pega Platform reports errors at design time and run time, and does not run any rule that includes any of the following Java code:

  • JavaCompiler
  • new ProcessBuilder()
  • org.dita.dost.invoker
  • Runtime.getRuntime()

For more information, see Configuring the Java injection check.

Improved offline support for mobile apps

Valid from Pega Version 8.4

The updated offline mode in Pega Platform™ now reduces implementation time, enhances the development process, and helps you create a more comprehensive mobile experience for users without a reliable web connection.

The improved offline support includes the following enhancements:

  • Offline-enabled apps now use native mobile UI components, such as headers and bottom bars.
  • Offline mode now supports decision trees for improved case processing. 
  • Users can now process multiple cases simultaneously in separate offline tabs, which leads to higher productivity.
  • Offline-enabled apps now work more efficiently because of improved caching and background synchronization.

For more information, see Working with offline apps.

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.

Descendant class instances now included in reports

Valid from Pega Version 7.2

The Report on descendant class instances option on the Data Access tab of the Report Definition rule has a new option to now include data from all descendant classes of the report's primary class. If descendant classes are mapped to multiple class tables, the generated SQL query performs UNIONs to include this data. Previously, only a single class was included in the report.

You can select a subset of descendant classes to include or exclude by adding a filter condition on pxObjClass.

Existing reports retain the older behavior for this option after an upgrade or update. To use the new option, you must set it for each existing report. New reports created in Designer Studio and out-of-the-box Pega 7 Platform template reports from which new reports are created in the Report Browser (pyDefaultReport and pyDefaultSummaryReport) default to the new option. If you have created custom template reports for some application classes, you must change them to enable the new option in reports that are created in the Report Browser for these classes.

See Reporting on data in multiple class tables.

Report Definition query filters can search embedded properties

Valid from Pega Version 7.2

Filter conditions on Report Definition rules that query the Elasticsearch indexes can now reference embedded properties. Previously, filter conditions could reference only the top-level properties of a class. To reference an embedded property within a filter condition, specify indexes for embedded page lists and page groups, for example, Customers(1).Addresses(1).City = Boston OR Customers(1).Addresses(1).State = MA.

These indexes are ignored in the generated query, and so can potentially match any value in a page list or group. However, filter conditions that reference multiple embedded properties in the same page list or page group, as displayed above, might not be satisfied on the same page.

BIX extracts can be scheduled and run from the Pega 7 Platform by using agents

Valid from Pega Version 7.2

You can create an agent that periodically invokes the new pxExtractDataWithArgs activity to run a BIX Extract rule. The activity takes the class and extract rule name, as well as an additional input string with a list of BIX command-line parameters, as input parameters to use for the run.

Report Definitions can query tables in multiple schemas

Valid from Pega Version 7.2

You can create a Report Definition that queries class tables in multiple schemas in the same database. Previously, queries on tables that were mapped to PegaRULES and PegaDATA schemas could not include tables that were mapped to other schemas, because other schemas were assumed to be in a different database. The schemas to which queried class tables belong are no longer validated when you save the Report Definition, so you can now query tables in schemas other than PegaRULES and PegaDATA. However, Report Definitions that query tables that are in more than one database fail when run.

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