Published Release Notes

Validate rule support in offline-enabled applications

To enhance the user experience of your offline-enabled application, you can now use validate rules that are referenced by a flow action. You can also explicitly add other types of validate rules as offline-supported. The offline validation API provides two methods that you can use in your custom code to run from a Run script action or a custom JavaScript function. Several JavaScript utility functions, the equivalent of built-in Java functions for Pega^® Platform, are now also available.

For more information, see Validate rule support in offline mode and Function rule support in offline mode.

Security enhancements in offline-enabled applications

To enhance the security of an offline-enabled application, you can now set the time period during which a user of an offline-enabled application stays logged in before the lock screen is displayed. The password, lockout, audit, and operator disablement security policy settings are supported in offline-enabled applications. For example, if a user enters an incorrect password several times and is locked out of the account, you can specify in minutes for how long the user is prevented from logging back in.

For more information, see Setting maximum login time.

OAuth 2 token support in Pega Mobile Client

The Client Store module in Pega Mobile Client has been extended to support OAuth 2 tokens. The tokens are used to authorize data synchronization requests that are sent to the Pega^® Platform. Once the OAuth 2 token support is turned on and configured on the server, Pega Mobile Client starts using it automatically. This functionality is available on both iOS and Android devices.

For more information, see Enabling data synchronization with OAuth 2 tokens.

No support for Android versions earlier than 4.4 on mobile devices

Pega^® Platform dynamic layouts by default now use Flexbox-based rendering. As a result, mobile devices running on Android versions earlier than 4.4 are not supported in Pega Platform. Such devices cannot render correctly with Flexbox because the Pega Mobile Client includes the default stock browser on the Android operating system.

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.

Attach Content control enhancements

You can now use the Attach Content control in Pega^® Platform to configure compression options that limit the size of files created on a mobile device. For example, you can choose from predefined settings to limit video duration or image size. These settings apply when the user records a new video or takes a new photo, but they do not apply to prerecorded media.

Also, when attaching content to a custom mobile app, users can now select any type of file from any source that is available in the device's native file picker component.

For more information, see Configuring file size options for the Attach content control.

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.

Change passwords from Pega Mobile Client

You can now change your Pega^® Platform password from a mobile device. After your password expires and you try to log in to a custom mobile app, Pega Mobile Client lets you define a new password and verifies it against active password policies.

For more information, see Enabling security policies.

Advance cases from a push notification screen

You can now approve and reject Pega^® Platform cases from your mobile device without opening a custom mobile app. Push notifications that you receive on a mobile device now display buttons that allow you to advance a case.

For more information, see Notifications.

Post Pulse messages to cases from a push notification screen

If your mobile device uses Android 7.0 or later, or iOS 9.0 or later, you can now respond to Pulse messages in Pega^® Platform cases without opening a custom mobile app. Push notifications received on a mobile device now display a Reply button so that you can respond immediately to the notification.

For more information, see Notifications.