Published Release Notes

Interactions in flows are no longer supported by the Run Interaction shape

The Run Interaction shape in flows has been replaced by the Run Data Flow shape, which supports running a single case data flow with a strategy. Flows that include the Run Interaction shape continue to work; however, you must now use the Utility shape to reference any new interactions that you create.

For more information, see Running a decision strategy from a flow and About Interaction rules.

Post Pulse messages to cases from a push notification screen

If your mobile device uses Android 7.0 or later, or iOS 9.0 or later, you can now respond to Pulse messages in Pega^® Platform cases without opening a custom mobile app. Push notifications received on a mobile device now display a Reply button so that you can respond immediately to the notification.

For more information, see Notifications.

Support for optimization of offline packaging during synchronization

You can now optimize offline packaging during full and delta synchronization of an offline-enabled application. Enabling this option for an offline-enabled application means that a case is packaged during delta synchronization only when a new work item for the case is added to the user's worklist and the case was not previously packaged during full or delta synchronization. The case is packaged during full synchronization only when the work item for the case exists in the user's worklist. This feature is useful in field service applications where field service agents usually work on existing assignments and do not need to create new cases.

For more information, see Offline packaging optimization during synchronization.

Pulse gadget for feeds from multiple data sources

You can now use the pxFeed gadget to change the information that you want to display in a Pulse activity feed. By customizing the gadget, you can allow users to post messages on the activity feed and show messages from multiple data sources, for example, comments that are posted on a user's team feed.

For information about Pulse enhancements, see Pulse enhancements for social collaboration.

Enhancements to rule comparison

For rules that contain a large amount of text, you can now highlight all the changes between rule versions and apply the changes from the version that the rule is compared with. By comparing versions, you can see what changed in the code and resolve conflicts. This ability to compare versions accelerates the development cycle, allowing for a faster time to market with higher quality code.

For more information, see Comparing rule versions.

Enable email notifications on agent failure

You can now get email notifications each time an agent fails with a PEGA0010 alert. By receiving notifications on agent failure, you can immediately take action to restart or fix the agent. You can enable email notifications on the Agent Management landing page.

For more information, see Enabling notification on agent failure and PEGA0010 alert: Agent processing disabled.

Download the system state information for a node and the cluster

On the Cluster Management landing page, you can now download a JSON file that contains information about the current system state for a single node or for the whole cluster. You can use this file to compare persisted system state information across time, which can be helpful in debugging system problems. You also can use a new REST API with third-party tools to download the system state file.

For more information, see Downloading the system state.

Select values gadget optimization enhancements

The Select values gadget includes several enhancements that help reduce performance issues when a data set is very large. Administrators and developers can now add and remove optimizations for fields directly in Designer Studio. Additionally, Select values gadgets were added to the proposition import shape and history shape in the Strategy rule form.

For more information about Select value gadgets and field optimization, see Optimizing properties in Select values gadget.

Enhanced approach for defining user actions

You can now define user actions, such as local actions and supporting processes for case types and stages, by clicking Optional actions on the Workflow tab. You can add user actions for case types in the Case wide actions section and for stages in the Stage-only actions section.

For more information, see User actions for case types and stages.

Life cycle tab renamed to Workflow

The Life cycle tab for case types has been renamed to Workflow. On the Workflow tab, you can define a life cycle for case types by clicking Life cycle, and you can define user actions for case types and stages by clicking Optional actions.

For information about defining a life cycle for a case type, see:

• Pega Express 7.3.1 – Defining a life cycle for a case type
• Pega Platform 7.3.1 – Defining a life cycle for a case type

For information about user actions, see:

• Pega Express 7.3.1 – User actions
• Pega Platform 7.3.1 – User actions