More action types on the bottom bar
Valid from Pega Version 8.3
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
Valid from Pega Version 8.3
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
Valid from Pega Version 8.3
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
Valid from Pega Version 8.3
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
Valid from Pega Version 8.3
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.
Support for decision tables in offline-enabled applications
Valid from Pega Version 8.3
You can now use decision tables to reduce the implementation time of your offline-enabled applications. By using decision tables you can further automate case processing and derive the logic from the data model. Decision tables can be referenced in a flow rule as a type of decision shape or called from the declare expression rule. No additional configuration is required to use decision tables in offline-enabled applications.
For more information, see Decision table support in offline mode.
Low-code styling in mobile apps
Valid from Pega Version 8.5
The mobile channel now supports enhanced low-code styling and branding of mobile apps. For example, you can customize app icons in three different ways: by uploading an image, by selecting from a list of font icons, or by using the default text-based icons. This enhancement helps you to conveniently customize the look of mobile apps to match the branding guidelines of your company and provide a consistent experience for users across different channels.
For more information, see Applying a custom theme to mobile apps.
Offline support for Cosmos-based mobile apps
Valid from Pega Version 8.5
Mobile apps that are based on the Cosmos design system now support offline mode. Previously, offline-enabled apps had to rely on the classic look. Now, you can use the low-code Cosmos solutions to design apps that operate reliably regardless of the connection status.
For more information, see Designing apps for offline mode.
Removal of Pega Mobile Client 7
Valid from Pega Version 8.5
You can now use a single Pega Mobile Client™ that improves app performance, app development, and meets all your mobile needs. With the introduction of new functionalities for mobile apps, Pega Mobile Client 7 is removed in Pega Platform™ 8.5.
Upgrade impact
After an upgrade to Pega 8.5, you can no longer build mobile apps based on Pega Mobile Client 7, and existing apps based on Pega Mobile Client 7 no longer connect to Pega Platform. App developers can now configure mobile apps with Pega Mobile Client.
What steps are required to update the application to be compatible with this change?
Existing clients that upgrade to Pega 8.5 are automatically switched to Pega Mobile Client.
Web portal reuse removed from the mobile channel
Valid from Pega Version 8.5
The reuse of web portals for creating mobile apps with a single web view is no longer supported. You can conveniently update your existing channels that reuse web portals to take advantage of the multiple-views experience and native mobile capabilities, such as native mobile list views or floating action buttons.
Upgrade impact
The Reuse web portal option is removed from Pega Platform 8.5 and later.
What steps are required to update the application to be compatible with this change?
App developers need to use the migration tool available on the mobile channel to move their apps to the recommended new navigation designer. When users open existing mobile channel with the Reuse web portal option configured, they are prompted to run through the wizard to upgrade the mobile channel to the latest Pega Mobile Client based configuration. When this is done, app developers should rebuild the app.