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.

Support for building apps as Android App Bundles

Valid from Pega Version 8.6.1

As of August 2021, Google Play Store requires that you submit new apps in the Android App Bundle publishing format instead of the APK format. You can now build Pega mobile apps in the Android App Bundle format so that they comply with this new requirement.

For more information about generating installation packages for Pega mobile apps, see Generating installation packages. For more information about the Android App Bundle publishing format, see the Android for Developers documentation.

Define and manage features during application development

Valid from Pega Version 7.3

You can now define and manage the features and child features that you want to implement in your application. A feature represents any capability in your application that you want to promote to stakeholders during the application development process. When you develop an application and design case types, you can link each case type to top-level features in Designer Studio. In addition, you can associate existing rules with features, which maintains traceability and makes it easier for you to extend the application because you can identify the rules that are associated with each feature.

For more information, see Features.

Improved capability to attach content in offline-enabled applications

Valid from Pega Version 7.3

The feature for attaching content in applications while in offline mode has been enhanced. A list of attached content is displayed in the application while in offline mode. You can view or delete attachments if the application has not yet been synchronized with the server. You also can change the maximum size of a file that you can attach while working in offline mode. This option gives you the flexibility to select the right size of attachment for a specific application for performance, memory limitation, or security reasons.

For more information, see Attach content support in offline mode.

Create connections to repositories

Valid from Pega Version 7.3

Pega® Platform can communicate with common repository technologies. Whenever an action creates a RAP, Pega Platform can browse, publish, or fetch artifacts: for example, when exporting an application, product, branch, or component. Repositories are instances of the Data-Repository class which holds all necessary connection information.

Pega Platform includes tools to connect with the following repository types:

  • JFrog Artifactory
  • Amazon S3

For more information, see Creating a JFrog Artifactory or Amazon S3 repository connection.

Fingerprint authentication in Pega Mobile Client

Valid from Pega Version 7.3

The authentication feature in Pega Mobile Client has been extended to support user credentials that are secured by a fingerprint reader. The FingerprintAuthenticator object and its methods replace the TouchID API. A compatibility layer has been created to support custom mobile apps that use the deprecated API. This functionality is available on iOS and selected Android devices.

For more information, see Authentication API.

Enhancement to the error and warning handling JavaScript API

Valid from Pega Version 7.3

During offline post processing of a flow in an application, you can now use the ClientCache JavaScript API to handle informational and warning messages in addition to error messages. Several ClientCache API JavaScript functions have been updated for this purpose. Informational, warning, and error messages are displayed when you submit a form, but only error messages prevent you from advancing the case.

For more information, refer to Error and warning handling API in offline mode.

New customization options for paused custom mobile apps on Android

Valid from Pega Version 7.3

You can now customize the presentation of a paused custom mobile app for Android. You can upload a custom status bar icon and customize the title and message that are displayed in the device's notification area. Also, you can use a new optional parameter of the startKeepAlive method of the Pega Mobile Client's Container API as an alternative way of setting the notification title.

For more information, see Customizing the paused Android app notification.

Support for round icons in Android 7.1 mobile apps

Valid from Pega Version 7.3

To improve the look and feel of Android mobile apps, round icons are now supported in apps that are created for Android 7.1. You can add the icons to the assets.zip file during the customization stage when you build the app in the Pega® Platform.

For more information, see Branding mobile apps.

Today widget for iOS custom mobile apps

Valid from Pega Version 7.3

The Pega Mobile Client has been extended to support a Today widget in custom mobile apps for iOS. By default, the Today widget displays the current user's list of work objects. This functionality is available only for offline-enabled custom mobile apps and requires that your certificate set include a widget provisioning file.

For more information, see Configuring a Today widget on iOS.

Validate rule support in offline-enabled applications

Valid from Pega Version 7.3

To enhance the user experience of your offline-enabled application, you can now use validate rules that are referenced by a flow action. You can also explicitly add other types of validate rules as offline-supported. The offline validation API provides two methods that you can use in your custom code to run from a Run script action or a custom JavaScript function. Several JavaScript utility functions, the equivalent of built-in Java functions for Pega® Platform, are now also available.

For more information, see Validate rule support in offline mode and Function rule support in offline mode.

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