Enhanced Wait shape
Valid from Pega Version 8.4
Pega Platform™ now supports the enhanced Wait shape that configures the case to wait for the resolution of all child cases instead of only the child cases of a specific type. When you set up the Wait shape to stop a case until it reaches a certain status, you can decide whether the shape considers statuses from a whole case life cycle, or only the statuses after the wait begins. The enhanced Wait shape provides you with greater control over resolution of your cases.
For more information, see Pausing and resuming processes in cases in Dev Studio, Pausing and resuming processes in cases in App Studio.
Case tags for improved case search
Valid from Pega Version 8.4
Pega Platform™ now supports enhanced tagging for case types so that you can search cases by tags. As a result, tagging is more consistent because you can define a set of suggested tags that users can add to their posts and cases. When users search for cases, they can apply several filters, for example, recently added or most frequently used tags.
For more information about tags, see Tagging cases in Dev Studio, Tagging cases in App Studio.
Case notification enhancements
Valid from Pega Version 8.4
Pega Platform™ now supports creating case notifications directly in Case Designer in App Studio and Dev Studio, so that you do not need to create a notification rule first and then provide the rule name in a case. You can speed up and simplify case creation by specifying recipients for each notification, without the need to create a data page for the recipients. Push notifications and email subjects can now also include properties, for example, a case ID or a goal and deadline.
For more information, see Sending event notifications from cases in Dev Studio, Sending event notifications from cases in App Studio.
Improved and simplified field-level auditing
Valid from Pega Version 8.4
To track the progress of your work and maintain the compliance of your cases, both App Studio and Dev Studio now support field-level auditing for case fields. Your application tracks and displays information about user updates to scalar fields, field groups, and field group lists, at any level of your case data model. For example, you can check previous and current field values, the last user to change the values, and the time of their modification.
For more information, see Track changes in cases with improved field-level auditing (8.4), Enabling field-level auditing in Dev Studio, Enabling field-level auditing in App Studio.
Creation of case documents in a case life cycle
Valid from Pega Version 8.4
To save time and further automate your business processes, Pega Platform™ now supports generating case documents as part of the case life cycle. You can ensure that the documents include all necessary information by first creating a document template in a word processor. When you create a template, you add dynamic tags that your application populates with relevant data unique to each case, for example, the case ID and current date. To make your documentation more meaningful, you can also include attachments.
For more information, see Generate case documents in a case life cycle (8.4), Generating case documents in Dev Studio, Generating case documents in App Studio.
Pulse configurations in the case type settings
Valid from Pega Version 8.4
In both App Studio and Dev Studio you can now configure Pulse in a simplified and user-friendly way, in the case type settings. Add Pulse posts to cases, define default and add new feed sources, and then customize the Pulse label, all without performing advanced actions, such as configuring sections. You can also define visibility conditions for each post type.
For more information, see Start collaborating faster with simplified Pulse configuration (8.4), Configuring Pulse for case types in Dev Studio, Configuring Pulse for case types in App Studio.