Published Release Notes

Support for controlling binary file upload in Pega Mobile Client

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

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

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

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

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.

The worklist appears to be empty when you go back from an opened case in an offline-enabled mobile application

In a Pega^® Platform offline-enabled application, when you go back to the worklist from an opened case, the worklist appears to be empty even though it contains cases. This issue will be fixed in the next release of Pega Platform. Only portals that use the key principles and design of the pyCaseWorker portal are supported in offline-enabled applications.

For more information, see Offline mobility guidelines.

Custom mobile app assets file validation at upload

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

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

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

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.