Post files and links with pxPostMessage API
Valid from Pega Version 7.1.4
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
Valid from Pega Version 7.1.4
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
Valid from Pega Version 7.1.4
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.
Case Manager option for searching only attachments
Valid from Pega Version 7.2
Case Manager search now has an option to search only case attachments. When you search attachments, a new column in the search results displays a paperclip icon with the number of attachments that match the search string. You can click the number to display a list of matching attachments for the selected case.
The Declarative Network display is now cross-browser compatible
Valid from Pega Version 7.2
The Declarative Network display can now be displayed on all browsers.
Label changes to field types in Case Designer
Valid from Pega Version 7.2
The following field types have been renamed in Case Designer to be consistent with Data Designer and other areas of the Pega 7 Platform.
| Label in previous versions | Label in Pega 7.2 |
|---|---|
| Text | Text (single line) |
| Text (multiple lines) | Text (paragraph) |
| Check box | Boolean |
| Date and time | Date & time |
| Date | Date only |
| Drop down | Picklist |
| Number (integer) | Integer |
| Number (decimal) | Decimal |
Users who upgrade from versions prior to Pega 7.2 do not have to take any action because the label changes are cosmetic and do not affect the underlying controls or property types that support form building.
For more information about the field types that you can use when building a form, see Storage and display of single-value fields.
New Pulse gadgets for developers
Valid from Pega Version 7.2
Pulse for the Pega 7 Platform provides two new gadgets: pxContextFeed and pxActivityFeed.
The pxContextFeed gadget is a section that you can integrate with your application. Users can use this gadget to communicate with other users by creating and sharing posts within a given context. You can also customize the gadget or build your own Pulse interface by using a number of APIs.
The pxActivityFeed gadget aggregates all the activity feeds for the cases that a user follows without requiring that individual cases for posts be viewed.
For more information, see the help topic Pulse gadgets and custom APIs.
New Pulse gadget for users
Valid from Pega Version 7.2
You can use Pulse to communicate and collaborate with other users. For example, in Pulse you can post messages, share files, select cases for which you want to receive emails, search for content, and view an activity feed in your dashboard that aggregates your Pulse posts.
For more information, see Pulse for social collaboration.
New types of steps in a process
Valid from Pega Version 7.2
You can add assignments, subprocesses, and preconfigured steps to a process in Case Designer. By using these new step types, you can quickly enhance your case life cycle and identify opportunities for reuse. This change also delivers a more consistent experience to users who are working in Case Designer and Process Modeler.
For more information, see Steps in the life cycle of a case.
Reusable components in a case life cycle
Valid from Pega Version 7.2
You can easily add an existing process or user action to the life cycle of a case type. By reusing functionality in your application, you can reduce the time that it takes to configure a case type.
For more information, see Steps in the life cycle of a case.