Published Release Notes

Package caching is not supported in offline-enabled applications built with the UI Kit 7 (09-01-01) portal

When you create an offline-enabled application in Pega^® Platform, by default, it uses a portal with the UI Kit 7 (09-01-01) ruleset. In such a case, the package caching functionality cannot be used. You must either disable caching on the Advanced tab of the Access Group rule form, in the Offline Configuration section, or use an adaptive design instead of rendering different elements for different devices with the UI Kit 7 (09-01-01) ruleset.

For more information, see Access Group form - Completing the Advanced tab.

No video controllers displayed on Android 4.3 and earlier versions

When you preview a video clip within Pega^® Mobile Client on a mobile device that runs Android 4.3 or earlier versions, video controllers are not displayed in full-screen mode.

Remote device log retrieval from online-only mobile apps

In addition to device logs from offline-enabled mobile apps, Pega Mobile Client™ can now upload device logs from online-only mobile apps. The upload to Pega Platform™ starts when a user restarts the mobile app. You retrieve device logs from a specific device to support remote users and troubleshoot mobile apps.

For more information, see Retrieving device logs.

Improved mobile user experience with spaces

Spaces in mobile apps have been enhanced to provide a wider screen area for navigation between content tabs such as Pulse, Boards, Subspaces, and Tasks. Mobile users can now use native selection controls to choose from the same space-specific actions that are available to users of desktop-based applications. The enhancement improves the usability of spaces and promotes collaboration between mobile users.

Spaces on mobile apps do not require any additional configuration.

For more information about spaces, see Collaborating with users by using spaces.

Increased display area in mobile apps

Mobile apps now support hiding the top and bottom bars when the user scrolls down. When the user scrolls up, the bars appear again. This enhancement improves the mobile user experience by presenting more data on the screen, for example, a longer list of items.

For more information, see Advanced layout options.

Mobile apps display skeletons for the initial screen load

Android and iOS mobile apps now display a skeleton before the initial screen loads, which enhances user experience and provides faster response to user actions on complex mobile screens or over slow networks. Until the initial screen is ready to be displayed, Pega Platform™ displays an empty placeholder that imitates the actual user interface.

Skeletons for the initial screen in mobile apps do not require any additional configuration.

File sharing improvements in custom mobile apps

Case management in custom mobile apps that are built for Android and iOS using Pega Infinity Mobile Client™ is now improved with the enhanced Attach content control. You can now attach files of any type from the device storage and from cloud services, for example, Google Drive or iCloud, or from other mobile apps that are installed on the device. Additionally, you can share any file attachments, except for signature files, in external mobile apps.

For more information, see Enabling attaching files to an application.

Support for Pega Infinity Mobile Client in offline-enabled applications

To take advantage of Pega Platform™ offline features, you can now build offline-enabled applications using Pega Infinity Mobile Client™. An offline-enabled application is built with Pega Infinity Mobile Client by default, and is fast to create and load. 

For more information, see Build offline-enabled applications using Pega Infinity Mobile Client, Offline-enabled application and Pega Infinity Mobile Client, and Pega Mobility and mobile clients.

New ClientStore JavaScript API for offline-enabled applications

For offline-enabled applications built using Pega Infinity Mobile Client™, you can now take advantage of a new window.pms.plugins.clientstore JavaScript API. The improved API is based on promises and events instead of callbacks and listeners, and replaces the previously available window.launchbox.PRPC.ClientStore JavaScript API which is now deprecated.

Native header with left and right actions for mobile apps

With Pega Infinity Mobile Client™, mobile apps can now use a native header with custom left and right actions for navigation. A native header standardizes the user experience of navigating between the screens of your app. For example, users can navigate to the previous screen with a swipe right gesture or the native back button.

For more information, see Enhancing a mobile app with the native header.