Published Release Notes

Decision logic added to surveys

You can now add decision logic to a survey to change the run-time order of questions. By defining a branch with conditions that skip or revisit questions, you can increase the flexibility of your survey.

For more information see Decision logic in surveys.

Add message header fields to the service email for Pulse email replies

The pzCreatePulseReply service email rule now has these additional fields in the message header: Message–ID, In–Reply–To, and References. As a result, the system interacts with email clients by using email headers when users reply to Pulse emails. If you configured a service email for replies to Pulse email notifications, add these fields to the service email to allow the system to post the replies in Pulse. If you are creating a service email, ensure that the message header and data have the same values as the values in pzCreatePulseReply.

For more information, see Enabling users to respond to Pulse email notifications.

Support for multiple attachments added to Pulse

You can now upload more than one attachment to posts and comments in Pulse. Because Pulse maintains the continuity of attachments in posts, email messages, and email notifications, you can use it to quickly follow conversations in a case.

For more information about the features that Pulse supports, see Communicating with Pulse.

Support for case references added to Pulse

You can now reference a case in a comment or post that you add to Pulse. By including a link in your message that opens a relevant work item, you can add context to a conversation.

For more information, see Enhancing a message in Pulse.

Quicker approach for reusing processes in a stage

You can now reuse processes more quickly in a stage when you define the life cycle for a case type. Reusing processes saves time and makes it easier to define processes for a stage instead of creating new ones. You can also reuse processes faster when you add parallel processes to a stage.

For more information, see Quick access for reusing processes in a stage.

Ability to annotate case attachments

Pega^® Platform application users can now add annotations to images that are attached to cases. For example, users can draw around an area of an image to highlight a faulty element of the device. Users can annotate all images, except for signature images or attachments that are stored in Pega Cloud or other external data stores. The annotated case attachments replace the original ones.

For more information, see Case attachment annotations.

Pega Survey documentation refers to deprecated field

The documentation for Pega^® Survey refers to the Answer Layout field on the Complex Question form, but this field is no longer supported. For more information about the question layout formats that Pega Survey supports, see Pega Survey.

Set the status of a case on stage entry

You can now set the status of a case when it enters a stage. By setting the status of a case on stage entry, you can communicate to stakeholders how close a stage is to resolution. For example, if a case is in the approval stage, you can set the status of the case to "Under review" when the case enters the stage.

For more information, see:

• App Studio – Changing the status of a case
• Dev Studio – Changing the status of a case

Resolve child cases with the parent case

You can now configure a stage to resolve open child cases when the parent case is resolved. Resolving child cases on the resolution of the parent case ensures that no child cases are left open when the parent case reaches the end of its life cycle.

For more information, see:

• App Studio – Configuring case resolution
• Dev Studio – Configuring case resolution

Conditionally skip a stage

You can now define a condition in App Studio and build an expression in Dev Studio that causes a case to skip a stage. The system evaluates the condition or expression at run time and skips the stage if a true value is returned. By skipping the current stage when it is not relevant, you can resolve a case more quickly by moving the case to the next stage in the sequence.

For more information, see:

• App Studio – Requiring conditions for stage entry
• Dev Studio – Requiring conditions for stage entry