Published Release Notes

Post files and links with pxPostMessage API

The pxPostMessageAPI now supports text messages, file attachments, and hyperlinks. You can programmatically update Pulse streams using this API from activities or SLA rules.

Case Management

This release has continued to focus on improving the functionality of the design environment with improvements to the Case Designer and stage configuration. Additional end user capabilities were also added to allow for processing a wider variety of cases, for those with and without stages and improved bulk processing handling.

• Flow action processing now uses the primary page instead of the interest page when using case/stage local actions, so that embedded flows are properly populated.
• Case-wide local actions rely on pzInternalStageFlow when there are no active, non-hidden assignments on the case. These case-wide local actions will now appear on a stage-less flow with no assignments.
• If a (valid) error is displayed in the outline view, saving or clicking around will not delete the error - the error will remain as a reminder to the developer to solve whatever problem is being flagged.
• May now add Cascading Approval validation and edit the parameters from the Case Designer Stage and Step page.
• Page labelling ("Page 1 of X") appears in the history list presented in the audit tab.
• The bulk processing feature has been enhanced.
• The Outline View functionality was changed so that the visible page will no longer refresh each time a flow is edited.
• The Post value was added to the instructions text field, so data isn't lost between nodes in the outline View.
• When Assign to Operator or workbasket is included as a filter, the bulk processing gadget is supposed to get a list of assignments. The UI for the results was enhanced for assignments to include a column for instructions so that the different assignments on the same work item can be distinguished.
• When designing a case type’s stages, it is no longer possible to skip the last stage (by using the "skip stage when" setting). When creating or editing the last stage, developers may no longer set a skip when rule; if tried, the system will display a warning and prevent that. If a Skip When rule is set up for a stage, and then all the intervening stages are deleted so that this stage becomes the last stage, the warning will display, and the Skip When rule will not be visible. If another stage is then added after that, the Skip When rule becomes visible again.
• When one or more locked work objects are processed using the Process Selected Items button, the action will be performed on the selected work objects. If the action is successful, a green tick appears on the work object. If it is not successful, a red cross will appear.
• When the topmost RuleSet in the RuleSet Stack is locked, customers may now open up Outline View by clicking "Configure Process Details" and make exploratory changes to experiment. Because the RuleSet is locked, these changes may not be saved, but the experiment can be tried.

Quickly create ad-hoc cases

The My Cases work area on the Case Manager portal introduces a Quick Create feature that lets users create cases and assign tasks that are not included in the processing of business cases (instances of case types defined in the Cases Explorer).  For example, a manager can create a case and a task to set up a phone conference with her staff, or a reminder to enroll in an online seminar. Users can also set up a series of tasks to represent all they work they need to do to accomplish a specific goal.

Class structure expanded for surveys and questions

You can now create surveys and questions at any class level. Because there is no longer a restriction on which class of flows can use the Survey and Question smart shapes, you can create more contextual surveys that reference embedded properties, or instances of classes, that you define outside the Work- class structure.

For more information about using the Survey or Question smart shapes in a flow, see Integration methods for surveys.

Locatable pages are deprecated

Locatable pages are deprecated. Use a data page instead. Data pages provide improved performance. When you save a rule that has a Locate Page Activity or when you create an activity of type Locate page, a guardrail warning is displayed indicating that this feature has been deprecated.

For information about data pages, see Data pages.

Like and bookmark Pulse messages

You can now like messages that are posted to Pulse and view the number of likes for each message. You can also bookmark the messages that you want to view in your activity feed.

For information about Pulse enhancements, see:

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

Real-time updates in Pulse

You can now view real-time updates of messages in Pulse. If a user posts a comment on a Pulse conversation while you are viewing the conversation, you receive a notification in real time, which you can click to refresh the conversation and see the comment.

For information about Pulse enhancements, see:

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

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.

Receive and reply to push notifications for Pulse messages

You can now receive push notifications on your mobile device when another user references you in a Pulse message or likes your messages in a Pulse conversation. You can both receive and reply to the push notifications that you get when another user posts on your profile, adds messages to a Pulse conversation in which you are involved, or posts comments on a case that you are following. To receive push notifications, select mobile push as a notification channel when you configure your notification preferences.

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

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.