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.

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.

Support for encrypted traffic in a cluster

Valid from Pega Version 7.3

The Pega 7 Platform includes the Ignite platform, which supports encryption for intra-cluster communications. You can now configure encryption for intra-cluster traffic for compliance with regulatory or organizational security requirements.

For more information, see Enabling encrypted traffic between nodes.

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.

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.

Attribute-based access control model

Valid from Pega Version 7.2.1

Attribute-based access control (ABAC) is a security authorization model in which access rights are determined through the use of policies and attributes. A policy decision engine in ABAC evaluates digital policies against available data (attributes) to permit or deny access to the requested resource. For example, you can now determine access rights to cases by examining security attribute values assigned to the user and the case.

For more information, see Attribute-based access control.

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

Valid from Pega Version 7.2.1

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

New hashing algorithm for Password property types

Valid from Pega Version 7.2.2

To provide extra protection against brute-force attacks, a new hashing algorithm has been added to the Pega 7 Platform. Bcrypt is used as a default hashing algorithm for Password property types. The bcrypt key setup algorithm takes a long time to process. This means that potential attackers would have to spend a substantial amount of time testing every possible key.

For more information, see Using the bcrypt hashing algorithm for Password property types.

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