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.
Configuring geolocation tracking at the case level
Valid from Pega Version 8.1
You can now enable geolocation tracking at a case level to track users of an offline-enabled custom mobile app. By tracking users who are working on a case, you can monitor or supervise them while they are using the custom mobile app and when the app is running in the background. You can also track users when the device is not connected to the server. Recorded locations are synchronized with the server and stored in a database that is available through a data page. When Pega Platform™ receives location data, the new Map control can display multiple user tracks and markers that represent other data, for example, job locations that are assigned to users.
For more information, see Tracking mobile end users with the Map control and Adding the map control.
Support for native search in custom mobile apps
Valid from Pega Version 8.1
To improve the overall user experience in a custom mobile app, you can configure native search in the user interface of the application. To use the search capability, first configure the pySearchConfiguration rule. This rule allows you to optionally define a set of search categories as a local data source. You then configure the mobile search action for any user interface control, for example, a button in a section. Users can tap the search field to see the most recent search results, including results that are grouped by categories, as they enter search text.
For more information, see Native search capability in custom mobile apps and Configuring search in custom mobile apps.
External login with OpenID Connect or SAML protocol for custom mobile apps
Valid from Pega Version 8.1
Custom mobile apps can now use single sign-on (SSO) with OpenID Connect or SAML to authenticate by using identity providers such as Google, Auth0, Okta, or Azure Active Directory (Azure AD). External login provides a convenient and secure way to access your application. Users' credentials are never shared with the custom mobile app.
For more information, see Configuring a custom mobile app to use external login with OpenID Connect or SAML protocol.
Support for multiple custom mobile apps for a Pega Platform application
Valid from Pega Version 8.1
To enhance the user experience and provide support for native mobile components, you can create multiple custom mobile apps for a Pega Platform™ application. For each custom mobile app, you must create a different mobile channel interface. In addition, you can configure each custom mobile app to run only in a specific portal for an application. The custom mobile app uses this portal regardless of which default portal is defined for the access group.
For more information, see Selecting a portal for a custom mobile app.