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 controlling binary file upload in Pega Mobile Client

Valid from Pega Version 7.4

The Client Store API of Pega® Mobile Client has been modified so that you can suspend and resume the process of uploading binary files to the server. You can also check the state of the file uploading process. As a result, custom mobile app users can process their work items without having to wait for the synchronization process to finish.

For more information, see Pega Mobile Client API methods for controlling binary data upload and Client Store API.

Support for large binary data item storage in Pega Mobile Client and offline case attachments in Pega Platform

Valid from Pega Version 7.4

Pega® Mobile Client can now store and synchronize large binary data items and their corresponding actions from the action queue on Android and iOS devices. As a result, custom mobile app users can view, attach, and delete data files, whether the device is online or offline. For this function to work, you must enable offline case attachment support, which allows your custom mobile apps to synchronize case attachments between the Pega Platform and the mobile device.

For more information, see Enabling offline case attachments support and Client Store API.

Improvements in the process engine for offline-enabled applications

Valid from Pega Version 7.4

The offline process engine includes several improvements. To provide more options when you develop an offline-enabled application, a decision shape as the first shape in a flow and parameters for the CreateNewWork action are now supported. Offline-enabled applications now also display information about the last data synchronization.

For more information, see Flow processing in offline mode.

Touch response supported on mobile devices

Valid from Pega Version 7.4

When displayed on a mobile device, all active elements of the Pega® Platform user interface now respond to touch by changing their appearance. No additional configuration is available or necessary.

Setting a build version of the custom mobile app

Valid from Pega Version 7.4

When you build a custom mobile app, you can now configure a build version and leave the custom mobile app version unchanged. This way you can upload an updated custom mobile app to the Apple App Store and Google Play Store without having to increment the app version.

For more information, see Setting the app build version.

Custom mobile app assets file validation at upload

Valid from Pega Version 7.4

When you build a custom mobile app, and upload branding assets or custom modules within a compressed file, Pega® Platform validates the file that you upload and displays confirmation and warning messages. For more information, see Uploading branding assets and custom modules.

New appearance of smart app banners

Valid from Pega Version 7.4

When you build a custom mobile app, you can use smart app banners to advertise your app. The look of these smart app banners has been modernized. Also, if you upload branding assets to customize the appearance of your custom mobile app, the smart app banners now display an icon that you upload as the main icon of your custom mobile app.

For more information, see Adding a banner for mobile app download.

Ability to delete the Mobile channel interface

Valid from Pega Version 7.4

When you build a Pega® Platform application, you can create a mobile app for your users. When you no longer need the mobile app, you can now delete an existing Mobile channel interface, just like any other channel that is available from the Channels and interfaces landing page.

For more information, see Channels and interfaces.

Improved Back button support in custom mobile apps for Android

Valid from Pega Version 7.4

In a custom mobile app for Android, you can press the Back hardware button to go back, instead of exiting the app. Custom mobile apps now function in the same way as native Android apps. For example, you can close a dialog box, dismiss an overlay, or collapse an expanded section by pressing the Back hardware button. On the home screen, pressing the Back hardware button displays a confirmation message before you can exit the app.

Support for Firebase Cloud Messaging (FCM) push notifications in Android custom mobile apps

Valid from Pega Version 8.2

You can now create Android custom mobile apps that use push notifications with the Firebase Cloud Messaging (FCM) services. The push notifications for Android custom mobile apps based on legacy Google Cloud Messaging (GCM) are deprecated, as GCM services will be officially removed from use on April 11, 2019. To continue to use push notifications, you must migrate your custom mobile apps to FCM services. Before building your custom mobile app, you must register your Android app for push notifications in the Firebase console, obtain the FCM server key and Google Services JSON file, and use the key and file in the Android certificate set to build the custom mobile app.

For more information, see Migrating Android custom mobile apps that use push notifications to Firebase Cloud Messaging, Push notifications in Android mobile app, and Android certificate set.

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