Published Release Notes

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.

Mobile search with sources from any data page

When you configure search for mobile apps, you create custom categories that limit the scope of the search and group the search results. In the previous versions of Pega Platform™, you had to add specific properties to the data page that you wanted to use as a source for a search category. Now, mobile search categories support any data page without modifications to help you effectively configure mobile search.

For more information, see Configuring categories for mobile search.

Faster starting offline-enabled mobile apps

Pega Platform™ and Pega Infinity Mobile Client™ now support access group data prepackaging when you build the executable files for an offline-enabled mobile app. This shortens the time needed to start a mobile app for the first time, because only the data that differs between the package and the current server state is synchronized. The data that is prepackaged comes from the access group cache, and you can decide what access group cache data should be excluded or additionally included in the package.

For more information, see Enabling access group data prepackaging during build.

More action types on the bottom bar

Pega Infinity Mobile Client™ now provides more flexible bottom bar configuration with a broader choice of actions, so that your apps can be more useful. For example, users can now create work items, open work items, or log out directly from the bottom bar of a mobile app.

For more information, see Configuring the bottom bar.

Data synchronization does not resume after mobile app restart

If an offline-enabled mobile app that you build with Pega Infinity Mobile Client™ is stopped during an initial data synchronization session, the data synchronization does not resume when the mobile app is restarted. Users must not stop the mobile app before initial data synchronization finishes.

For more information about data synchronization, see Offline capability and Guidelines for creating an offline-enabled application.

Ability to support advanced device features with Pega Infinity Mobile Client

Pega Infinity Mobile Client™ now provides a development kit that you can use to make mobile apps support advanced device features that are typically available to native applications, for example, an embedded laser scanner or a projector module, and integrate functions of external software solutions, for example, a cloud-based file storage.

For more information about enhancing mobile apps with device feature support, see the documentation for the development module in the latest Pega Infinity Mobile Client distribution package on Digital Delivery.

Swipe actions in repeating dynamic layouts in a mobile app

Lists that are based on repeating dynamic layouts now support swipe actions. The menu of available actions, such as Edit or Delete, does not obscure the view and is displayed only when a mobile app user swipes a row. Users benefit from easier navigation and they can do smaller tasks quickly, without leaving the main screen.

For more information, see Configuring swipe actions for a mobile app.

Indicate download size in offline-enabled mobile apps for iOS

When you publish a client-based mobile app in the Apple App Store that needs to download additional resources before it starts, the app must indicate the size of the download and obtain user consent. To comply with this requirement, you can now build offline-enabled mobile apps that prompt the user before they perform the initial data synchronization. If the user chooses not to download data, the application closes.

For more information about disclosing the data size and how the data size is calculated, see Defining advanced offline configuration for an access group.