Push notification delivery to multiple devices
Valid from Pega Version 7.2.1
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.
Support for subflows and decision flow results in offline mobile apps
Valid from Pega Version 7.2.1
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.
Support for error handling API in offline mobile apps
Valid from Pega Version 7.2.1
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.
Application administrators can send push notifications
Valid from Pega Version 7.2.1
From the Push Console application, administrators can send push notifications to custom mobile app users. Notifications sent from the Push Console can contain application-wide messages, for example, when an update is available for manual download.
For more information, see Push Console landing page.
Device preview includes a configurable list of common mobile devices
Valid from Pega Version 7.2.1
Pega Express device preview displays your application in a simulated mobile device. By previewing your application, you can view the user experience on a desktop, tablet, or phone. You can select from a list of common devices or add devices to the list by editing Pega-DevicePreview-Device.
For more information, see Previewing an application on a mobile device.
Transition effects for actions in custom mobile apps
Valid from Pega Version 7.2.1
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.
Goal and deadline push notifications in mobile apps
Valid from Pega Version 7.2.1
For mobile apps, you can enable push notifications to be sent to an assignee's or a manager's mobile device when a defined goal or deadline interval related to a service-level agreement expires. These notifications help caseworkers resolve cases on time.
For more information, see Requirements for goal and deadline push notifications.
New notifications for case types
Valid from Pega Version 7.2.1
You can now enable email and push notifications for a case type to communicate an event, such as an expired service-level agreement, to users in your application. By calling attention to assignments in a case that require action, you can help users to resolve cases faster.
Assignments in upgraded flows automatically inherit the notification policy that is defined by the case type unless you provide a custom notification activity or explicitly disable notifications in the Assignment shape.
For more information, see: Case notifications.
Ignore browser and operator locale to display Designer Studio in English
Valid from Pega Version 7.2.1
The operator preferences configuration includes the option to ignore the browser and operator locale. Some rulesets are shared between Designer Studio and end-user portals. Translated words might occasionally display in Designer Studio. Selecting the Ignore locale check box ignores the locale of the operator and browser to display Designer Studio portals in U.S. English only.
For more information, see Updating Designer Studio preferences.
Ignore locale settings requires refresh after server restarts
Valid from Pega Version 7.2.1
The Ignore locale check box in operator preferences is selected to display Designer Studio in U.S. English. After a server restarts, screens initially ignore this setting. When the screen is refreshed or reopened, the screen is rendered as expected.