The Run Data Flow shape replaces the Run Interaction shape
Valid from Pega Version 7.3.1
The Run Interaction shape in flows has been replaced by the Run Data Flow shape to introduce a consistent way of making decisions and capturing responses. You can now run a single-case data flow by referencing the data flow in the Run Data Flow shape. The data flow must have an abstract input and abstract or dataset output.
For more information, see Running a decision strategy from a flow, About Data Flow rules and Interactions in flows are no longer supported by the Run Interaction shape.
Interactions in flows are no longer supported by the Run Interaction shape
Valid from Pega Version 7.3.1
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.
Pulse gadget for feeds from multiple data sources
Valid from Pega Version 7.3.1
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
Valid from Pega Version 7.3.1
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
Valid from Pega Version 7.3.1
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
Valid from Pega Version 7.3.1
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
Valid from Pega Version 7.3.1
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.
Create simple URLs for work objects
Valid from Pega Version 7.3.1
You can now represent your work objects with simple URLs by using the new URL Mappings rule. Simple URLs are meaningful and easy to share with others, and improve collaboration between users of the same Pega® Platform application. You can define different URL patterns to use in your application for your work objects (cases), reports, landing pages, or others. You can also generate canonical URLs for your case types to make all instances of these case types searchable by third-party search engines. To enable search engine indexing, a link tag is added to your case object harness.
For more information, see URL Mappings.
Enhanced activity feed for Pulse displays messages
Valid from Pega Version 7.3.1
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
Valid from Pega Version 7.3.1
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.