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.

PegaDATA connection settings now required in the prconfig.xml file

If you use the default prconfig.xml file that is included with Pega^® Platform, and you have not removed the PegaDATA connection settings, no action is required. If you use a custom prconfig.xml file, for example, for running tests, ensure that the database connection settings for PegaDATA are not blank.

For more information about the connection settings, see PegaDATA connection settings in the prconfig.xml file.

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.

Node classification replaces NodeID-based configuration

For simpler cluster administration and better application resiliency, Pega^® Platform is moving toward a node classification model. Although agents will continue to work by using NodeIDs for several upcoming releases, use node types instead of NodeID configuration for agents, listeners, and decisioning services for more efficient operations and upgrades.

For more information, see Node classification.

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 Cloud Services File Storage service

Pega Cloud Services introduces Pega Cloud Services File Storage, a service that is fully integrated with the Pega Platform to support your Pega applications. New subscriptions and upgrades to the latest Pega Platform version make this the default storage repository.

For more information see Pega Cloud Services File Storage.

Pega Cloud Services introduced this new service as of QI 2018.

Support for Java 8