Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Limited question and answer formats in new surveys

Valid from Pega Version 7.4

Complex questions and some answer formats for simple questions, such as attachment, are not supported by the new surveys that you create. Although you can create stand-alone questions in your survey library that use these formats, you can add these questions to legacy surveys only.

For more information about supported answer formats, see Answer formats for questions in a survey.

Improved survey authoring

Valid from Pega Version 7.4

You can now add functionality, such as validation and visibility conditions, to a survey without having to manage multiple rule forms. By using the centralized options on the Survey Management landing page, you can visualize changes to survey items in real time and configure surveys more quickly.

For more information about improved options, see Streamlined survey configuration.

Decision logic added to surveys

Valid from Pega Version 7.4

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

Valid from Pega Version 7.4

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

Valid from Pega Version 7.4

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

Valid from Pega Version 7.4

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

Valid from Pega Version 7.4

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

Valid from Pega Version 7.4

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.

Business logic-based routing to process cases more efficiently

Valid from Pega Version 8.3

Process cases more efficiently by defining business logic-based routing options to route tasks to customer service representatives (CSRs) who have a specified availability or skillset. For example, you can ensure that a task is routed to a CSR with a high level of a German language if it is your business need. You can also create custom lists of operators and work queues to filter CSRs who can receive an assignment.

For more information, see Choosing an assignee at run time in Dev Studio, Choosing an assignee at run time in App Studio, Configuring business logic-based routing APIs.

Task board enhancements for improved tracking of tasks

Valid from Pega Version 8.3

App Studio and end-user portals, such as Case Manager, now provide an enhanced task board which helps you improve collaboration on task resolution. For example, you can create a checklist within a task, and then update the checklist to inform other users about the progress of the task. Attach content to a task to ensure that all users have the information that they need, and to make tasks more meaningful. Now you can also categorize tasks, and then filter them by category, to quickly access relevant information.

For more information, see Monitoring and tracking tasks in Dev Studio, Monitoring and tracking tasks in App Studio.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us