This content has been archived.
Close popover

What's new in Pega Mobile Client

These release notes provide information about enhancements and known issues that were resolved in each Pega Mobile Client release.

Release notes for 7.x versions

Release notes for 6.x versions

Release notes for 7.x versions

Current version

The following enhancements have been implemented.

7.41.3

  • Pega Mobile Client supports iOS 12.1. You must use Xcode 10.1.x to develop custom modules for iOS.
  • Support for the prepackaging of a custom login page in a custom mobile app
    If you want your custom mobile app to display a login page regardless of the state of data connection, you can use the Mobile channel page to prepackage a custom login page. For more information, see Packaging user interface files in a custom mobile app.

Supported platforms

  • Device platform support: Android 4.0.3 and later, iOS 9.0 and later.
  • PegaPlatform support: Pega Platform 7.2.2, 7.3.0, 7.3.1, 7.4.0, and 8.1.0.

Previous versions

The following enhancements have been implemented.

7.41.2

  • Support for Firebase Cloud Messaging
    If you are building Android custom mobile apps that use push notifications, they now support the new messaging service from Google. For more information, see Migrating Android custom mobile apps that use push notifications to Firebase Cloud Messaging.
  • No delay for the last batch of synchronized offline actions
    When your offline-enabled custom mobile app sends Client Store content and actions to the Pega Platform server, actions are now processed on the server, and removed from the client, immediately after the last batch of actions is transmitted.
  • Enhancements to overall performance of the product.

7.41.1

  • Pega Mobile Client now supports iOS 12.0. You must use Xcode 10.0.x to develop custom modules for iOS.
  • Enhancements to overall performance of the product.

7.41.0

  • Support for external login with OpenID Connect or SAML
    Pega Mobile Client now supports single sign-on (SSO) with OpenID Connect or SAML authentication by using identity providers such as Google, Auth0, Okta, or Azure Active Directory (Azure AD).
  • Ability to use a device lock to protect a custom mobile app
    If the custom mobile app uses external login with OpenID Connect or SAML authentication, it can be protected with the device's personal identification number (PIN) or biometric lock.
    For more information, see Protecting your custom mobile app with a device lock.
  • Possibility to turn off app data clearing on iOS
    You can now disable the functionality that clears custom mobile app data when exiting the app. To do this, set the container.ios.disableClearCache to "true" in the custom.properties file.
    For more information, see Overriding Channels and interfaces form settings with custom parameters.
  • Support for native search
    Pega Mobile Client now uses a native search gadget that is faster and more responsive because it points to a local store.
    For more information, see Support for native search in custom mobile apps.
  • Support for user geolocation configured at case level
    User location data can now be recorded if tracking is enabled for a case that is present on the user's work list.
  • Support for offline data synchronization request chunking
    Pega Mobile Client can now resume data synchronization from where it stopped due to communication failure. You can also set the size of a number of actions within a single data synchronization request.
    For more information, see setMaxNumberOfActionsPerRequest.
  • Support for authenticating push messages with OAuth tokens
    Pega Mobile Client does not use additional access tokens for push notification actions any more. It reuses the primary authentication tokens instead.
  • Support for request tracing for the debugging builds
    If you are using Android devices newer than 7.x, you can now trace HTTP requests by using a proxy. To learn how to do this, see Changes to Trusted Certificate Authorities in Android Nougat on the Android Developers Blog website.

7.40.3

  • Enhancements to overall performance of the product.

7.40.2

  • Enhancements to overall performance of the product.

7.40.1

  • Enhancements to overall performance of the product.

7.40.0

  • Enhancements to overall performance of the product.

  • Support for user authentication with OAuth 2.0 server in ROPC mode
    The Authentication API can now authenticate the user by sending credentials to an independent OAuth2 server that operates in Resource-Owner-Password-Credentials mode in order to obtain an access token. The access token is then used to connect to the Pega Platform. By using this functionality customers can keep the authentication process under their control.
    For more information, see PegaAuthenticator.

Release notes for 6.x version

Current version

The following enhancements have been implemented.

6.21.7

  • Pega Mobile Client now supports iOS 12.0. You must use Xcode 10.0.x to develop custom modules for iOS.
  • Enhancements to overall performance of the product.

Supported platforms

  • Device platform versions: Android 4.1 and later, iOS 9.0 and later
  • Pega Platform versions: Pega 7.1.8 to 7.2.1 (with hotfixes)

Previous versions

The following enhancements have been implemented.

    6.21.6

    • Pega Mobile Client now supports iOS 11.0. You must use Xcode 9.0.x to develop custom modules for iOS. Also, Pega Mobile Client now supports Android 8.0. For more information, see the supported platforms below.

    6.21.5

    • Pega Mobile Client now supports iOS 10.3. You must use Xcode 8.2.x to develop custom modules for iOS.
    Suggest Edit

    Have a question? Get answers now.

    Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.