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.

Case Management

Valid from Pega Version 7.1.3

This release had a focus on extending key capabilities to improve the ease of configuration based on early adopter feedback.  Improvements were made in run-time performance, especially in high volume situations with complex case configurations.  A series of cosmetic changes and fixes are included.

  • The Wait shape now supports dynamic references.
  • Issues were addressed with the CreatePDF and the CascadingApproval Smartshapes.
  • Attachments have been improved.
  • Issues with the Create Case Type functionality were addressed.
  • The Pega Pulse functionality has been improved, including its performance.
  • When auditing a work item, History is now the default tab.

Issue with the Sandbox directive on the Content Security Policy rule form has been fixed

Valid from Pega Version 7.2.2

An issue that related to the Sandbox directive not being applied, even after a value in the Content Security Policy rule form was selected, has been fixed. As a result, restrictions that are applied based on the settings in the Sandbox directive are now more closely aligned with the World Wide Web Consortium (W3C) specification than in previous releases. You should test your Content Security Policy to ensure that this change does not cause unexpected behavior in your application, such as making the security policy too restrictive.

Multiple notifications are delivered for the same Pulse post

Valid from Pega Version 7.3

When a user posts a Pulse comment, the users who subscribe to the activity feed might receive more than one notification if the posted comment triggers several notification rules.

For example, when a user posts a comment on a case that he or she follows, any response to the comment can result in the following notifications:

  • Notification when a new comment is posted on the followed case (triggers the pyAddPulsePost notification definition)
  • Notification when a comment is a response to the user’s original post (triggers the pyAddPulsePost notification definition)
  • Notification when the user is mentioned in the comment (triggers the pyAddUserMentionedPost notification definition)

Surveys are not compatible with prior versions of the UI Kit

Valid from Pega Version 7.3

Now that survey functionality is available in the Pega-Survey ruleset, some rules are no longer compatible with prior versions of the UI Kit. To ensure that your surveys are rendered correctly, update your Application form to include version 09.01 of the UI Kit.

If you cannot change the version of the UI Kit, you can override the Work-.pyCaseActionArea section in your application and update it to use the same configuration as the section in version 09.01 of the UI Kit.

Surveys do not display navigation links

Valid from Pega Version 7.3

The navigation links, or bread crumbs, in a survey are not displayed when you configure a survey to run as a screen flow. To resolve this issue, override the Work-.pyCaseActionArea section in your application, and then update that section to include the Work-.ProcessSteps_ScreenFlow section.

Surveys do not display questions with custom templates

Valid from Pega Version 7.3

Because many rules have been refactored or renamed in the Pega-Survey ruleset, questions that use custom templates are not displayed in surveys. To resolve this issue, create a new version of the applicable sections from the Embed-PegaQ-Results-Question class in your application, and then update the sections to include your custom content and logic.

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.

Known issue: SAML IdP import uses only the last certificate

Valid from Pega Version 7.4

When you configure the identity provider for a SAML SSO authentication service, the backing keystore rule for the verification certificate is created with only the last certificate from the IdP metadata, instead of using all of the certificates. 

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