Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Low-code styling in mobile apps

Valid from Pega Version 8.5

The mobile channel now supports enhanced low-code styling and branding of mobile apps. For example, you can customize app icons in three different ways: by uploading an image, by selecting from a list of font icons, or by using the default text-based icons. This enhancement helps you to conveniently customize the look of mobile apps to match the branding guidelines of your company and provide a consistent experience for users across different channels.

For more information, see Applying a custom theme to mobile apps.

Offline support for Cosmos-based mobile apps

Valid from Pega Version 8.5

Mobile apps that are based on the Cosmos design system now support offline mode. Previously, offline-enabled apps had to rely on the classic look. Now, you can use the low-code Cosmos solutions to design apps that operate reliably regardless of the connection status. 

For more information, see Designing apps for offline mode.

Enhanced search in the mobile channel

Valid from Pega Version 8.5

The search configuration now includes up to three additional secondary fields, such as the case ID, category, cost, date, owner, and active channel. The enhancement increases the usability of search on mobile apps and provides more contextual information in the search results.

For more information, see Adding a search gadget.

Improved mobile channel user experience

Valid from Pega Version 8.5

Mobile channel authoring now includes two significant enhancements to the user experience. The new instant run-time preview makes security configuration more convenient. In addition, the offline tab is now present by default, to help you build offline-enabled mobile apps and complete assignments in areas with limited connectivity.

Enhanced swipe support for case actions

Valid from Pega Version 8.5

UI authoring in the mobile channel now offers more case-wide actions that can be performed by swiping on list items. For example, you can add a swipe action to attach an invoice to your expense work item. This enhancement increases usability and work efficiency as it allows for fast, instinctive mobile interactions.

For more information, see Designing a new mobile list page.

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.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us