Published Release Notes

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.

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.

Support for optimization of offline packaging during synchronization

You can now optimize offline packaging during full and delta synchronization of an offline-enabled application. Enabling this option for an offline-enabled application means that a case is packaged during delta synchronization only when a new work item for the case is added to the user's worklist and the case was not previously packaged during full or delta synchronization. The case is packaged during full synchronization only when the work item for the case exists in the user's worklist. This feature is useful in field service applications where field service agents usually work on existing assignments and do not need to create new cases.

For more information, see Offline packaging optimization during synchronization.

Support for Firebase Cloud Messaging (FCM) push notifications in Android custom mobile apps

You can now create Android custom mobile apps that use push notifications with the Firebase Cloud Messaging (FCM) services. The push notifications for Android custom mobile apps based on legacy Google Cloud Messaging (GCM) are deprecated, as GCM services will be officially removed from use on April 11, 2019. To continue to use push notifications, you must migrate your custom mobile apps to FCM services. Before building your custom mobile app, you must register your Android app for push notifications in the Firebase console, obtain the FCM server key and Google Services JSON file, and use the key and file in the Android certificate set to build the custom mobile app.

For more information, see Migrating Android custom mobile apps that use push notifications to Firebase Cloud Messaging, Push notifications in Android mobile app, and Android certificate set.

PEGA0107 alert enables performance monitoring of offline-enabled apps

You can now monitor the performance of offline-enabled apps by analyzing PEGA0107 alerts from Pega Predictive Diagnostic Cloud™. PEGA0107 alerts are equivalent to PEGA0069 alerts in the context of offline-enabled applications, but PEGA0069 alerts are not generated for offline-enabled applications.

For more information, see PEGA0107 alert: Client page load time for offline-enabled applications and Pega Predictive Diagnostic Cloud Improvement Plan overview.

Mashup code preview in App Studio

When you create a mashup channel for your application, you can now eliminate issues with the code and create better looking applications, by using the portal preview in App Studio. You can preview a channel to verify that different types of devices correctly display the mashup code. The preview functionality uses a default wrapper that functions as a portal for displaying a frame with the mashup code. You can modify the appearance of the default wrapper, and adapt the mashup user interface in design mode to meet your requirements.

For more information, see Configuring the Mashup channel and Previewing an application.

Default support for the OAuth 2.0 framework in custom mobile apps

You can now build custom mobile apps by using Pega Infinity Mobile Client or Pega Mobile Client 7 with the OAuth 2.0 authorization code grant flow that is enabled by default. This industry-standard authorization framework increases the security of custom mobile apps. Set up your application to either redirect to a login screen of a specific identity provider, or display a selection of available identity providers upon login. Settings for authentication services are now applied automatically when you build your app. You can ensure that a custom mobile app is secure by using a protection schema, such as a biometric sensor or a custom pin.

For more information, see Build secure custom mobile apps with the OAuth 2.0 framework.

Mobile channel enhancements

The Mobile channel now supports several enhancements to Pega Infinity Mobile Client™ and provides custom mobile app options that are arranged in a more intuitive, consistent, and convenient layout. By default, custom mobile apps that you configure within the Mobile channel are generated with Pega Infinity Mobile Client. You can choose between a single webview web portal or a multi webview application layout, and configure such options as: bottom bar navigation rule, the bottom bar style, and the full screen search widget. You can also build a custom mobile app with Pega Mobile Client 7, or select a specific version of the client application.

For more information, see Configuring a custom mobile app.