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.

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.

Debugging data synchronization issues with offline-enabled applications

Valid from Pega Version 7.2.1

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.

Building custom mobile apps that require a password to start

Valid from Pega Version 7.2.1

To provide extra protection of local data, you can now require user passwords for custom mobile apps. Requiring a password can increase the app's initiation time, but additional protection might be needed for applications that store sensitive information. In Designer Studio, on the Mobile tab, select Enforce user password on start to require user passwords.

For more information, see Configuring password enforcement.

Building custom mobile apps based on an explicit version of Hybrid Container

Valid from Pega Version 7.2.1

You can now lock the version of Hybrid Container on which your custom mobile app is built in Designer Studio. Locking the version helps avoid compatibility issues with the devices that are used in your organization. To lock the version of Hybrid Container, you must set the version in a .pyHCBuildVersion declare expression for a specific application.

For more information, see Building custom mobile apps based on a selected version of Hybrid Container.

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

Valid from Pega Version 7.2.1

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.

Flexbox layout mode for dynamic layouts

Valid from Pega Version 7.2.1

The flexbox layout mode is available for dynamic layouts and is now the default layout mode for newly created dynamic layouts. In a flexbox layout, sections contained within the layout can grow or shrink to fit the available space, providing a more efficient way to distribute space between items in a container. Existing dynamic layouts can be converted to the flexbox layout mode. You can configure the layout mode on the Presentation tab of the Dynamic Layout property panel.

For more information, see Dynamic Layout Properties — Presentation tab.

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