Published Release Notes

The Run Data Flow shape replaces the Run Interaction shape

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

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

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.

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

Create simple URLs for work objects

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

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

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.

Agile Workbench supports bulk actions

You can now create stories in bulk by importing a story template to Agile Workbench. By defining stories in bulk before you start development, you can size your project more quickly.

For more information, see Bulk actions in Agile Workbench.

Guided tours and online help added to application guides

You can now create application guides that display content from a Pega^® Platform help topic or a sequence of tour stops in a guided tour. By providing supporting information in an interactive format, you can help users complete tasks more quickly.

For more information about displaying help topics, tour stops, and other types of information in a task, see Interactive tasks in an application guide.