Published Release Notes

Support for advanced text analysis when routing incoming emails

You can use text entity, category and sentiment analysis during the automatic routing of incoming emails. You provide text analysis of the text-based email content by defining routing rules, so that an automatic decision is made about how to process the received emails by the Pega^® Intelligent Virtual Assistant. You can route the email content to an operator, assign it to a work queue, or open a top-level case with the information.

For more information, see Configuring routing conditions for automatic email handling.

Conditional paths added to case life cycle

You can now add a conditional path to a process in the life cycle of a case. By defining the decisions that cause a process to follow different paths, you can create cases that support more than one outcome.

For more information about conditional paths, see Conditional paths in a case life cycle.

Use of the @java function in expressions is deprecated

Use of the @java function in expressions is deprecated. Use a utility function or other product feature instead.

For more information about expressions, see Building expressions with the Expression Builder.

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.

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

Test when rules by using PegaUnit automated tests

You can now create and run PegaUnit automated tests for when rules. These tests reduce the testing effort required for when rules and improve product quality. They also help to identify issues that might be introduced in new releases by providing quick automated regression testing.

For more information, see Unit testing a when rule.

Enhanced activity feed for Pulse displays messages

The activity feed for Pulse has been enhanced to display replies to messages that you have posted, messages on cases that you are following, messages in which you are referenced, messages posted on your user profile, messages by users that you are following, and messages that you have bookmarked. You can filter the activity feed to display the messages that you want to view.

For information about Pulse enhancements, see:

• Pega Express 7.3.1 – Communicating with Pulse
• Pega Platform 7.3.1 – Pulse enhancements for social collaboration

Support for email triaging of interaction cases for the Email user channel

You can now triage customer email content that is saved in an interaction case for the Pega^® Intelligent Virtual Assistant for Email. A customer service representative can reply to the email, reassign the interaction case to another user or a work queue, resolve the interaction case, or spin off a business case from the interaction case. Carrying out these actions improves the artificial intelligence capability of the Pega Intelligent Virtual Assistant for Email, for example, for automatic email routing purposes.

For more information, see Email triage an interaction case.

Define property value criteria for stage entry

You can now define the criteria that property values must meet to enter a stage, by clicking Validations on the Data model tab of a case type. By validating the properties, you can ensure that a case contains relevant data before it enters a stage.

For more information, see Property condition requirements for stage entry.