Published Release Notes

Open cases in a mobile app with push notifications sent from Pega 7 Platform applications

Push notification smart shapes in a workflow of a Pega 7 Platform application can now send push notifications that open a case in a custom mobile app. Users working in the field can use this feature to instantly access priority assignments instead of having to search for changes manually.

For more information, see Configuring the Push Notification shape.

Cannot send mobile push notifications when the Pega 7 Platform is hosted on WebSphere Application Server

Push notifications are not sent to Android or iOS mobile apps when the Pega 7 Platform is hosted on WebSphere Application Server.

Debugging data synchronization issues with offline-enabled applications

If an offline-enabled mobile application that originates from the Pega 7 Platform fails to synchronize data after reconnecting to the server, the Pega 7 Platform generates a PEGA0066 alert. The alert includes detailed information about the failure, such as the activity that preceded the event, entries collected from the native application, and entries from the JavaScript part of the Pega 7 Platform application. The administrator can use the alert and device logs to facilitate error analysis and debugging without having to access the failing device.

For more information, see Understanding the PEGA0066 alert - Mobile App Data-Sync Failure.

Push notification delivery to multiple devices

Push notifications sent from the Pega 7 Platform are now delivered to all devices on which a user is logged in to your custom mobile app, regardless of the device platform. You can either send push notifications from the Push Console to all users who have your application installed on their devices, or configure your application to send push notifications to indicate that an action might be required, a status update is available, or a case was approved.

Transition effects for actions in custom mobile apps

Custom mobile apps that are developed on the Pega 7 Platform can include built-in transition effects that animate your forward or backward movement in cases that use flows. This feature adds to the look-and-feel experience of the custom mobile app.

You can also manually add a transition effect to actions that do not support built-in effects by using the Run Script action and calling the pega.desktop.setNativeTransition() JavaScript method.

For more information, see Transition effects on actions.

Support for error handling API in offline mobile apps

During the processing of cases in offline-enabled mobile apps, you can use several JavaScript API methods to perform error handling. You can now determine whether an error condition results from the post-processing of a flow or a subflow. You can also set, clear, or obtain the number of error messages on a property or a page while working in offline mode, similar to when you are running a Pega 7 Platform desktop application. When you run a custom mobile app in offline mode, you can submit a form, but you cannot move the flow forward until all the errors on a page and in the page's properties are resolved.

For more information, see Error handling in offline mode and Error handling API in offline mode.

Support for subflows and decision flow results in offline mobile apps

Subflows in offline-enabled mobile apps are now supported to perform additional tasks outside of the main flow. The subflow can run only on the current work item, with the subflow displaying in the main flow, in a nested subflow, or located next to an assignment. No likelihood routing is supported for subflows. It is also possible to set a flow result by using the pega.process.flow.setFlowEndStatus() JavaScript method to override the status set by a property in the subflow's end shape. The process engine also takes into account the likelihood setting if the flow result is conflicting or absent, provided the flow result is not in a subflow.

For more information, see Flow processing in offline mode.