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.

Email approval and instantiation not supported on multitenant systems

Valid from Pega Version 7.2.1

The Enable email approval check box appears on the General tab of an approval step in Case Designer in multitenant systems. It also appears on the Approval shape in Designer Studio. In addition, in Designer Studio, the Settings tab in Case Designer displays the option to configure email instantiation. However, because configuring email listeners is not supported on multitenant systems, you cannot enable email approval or email instantiation.

Ignore locale settings requires refresh after server restarts

Valid from Pega Version 7.2.1

The Ignore locale check box in operator preferences is selected to display Designer Studio in U.S. English. After a server restarts, screens initially ignore this setting. When the screen is refreshed or reopened, the screen is rendered as expected.

Flexbox-based dynamic layouts not supported for Android 4.4 and earlier

Valid from Pega Version 7.2.1

Flexbox-based dynamic layouts are not supported in Android 4.4 and earlier. When developing applications to be used on devices running Android 4.4 and earlier, use the inline-block layout mode for dynamic layouts.

Upgrade utility for Get Next Work performance

Valid from Pega Version 7.2.2

You can run a utility to upgrade Get Next Work processing to more quickly process assignments that were created in versions of the Pega 7 Platform earlier than 7.2.2. Performance is automatically improved on new installations.

For more information, see Upgrading Get Next Work performance.

Empty properties are not included in snapshot

Valid from Pega Version 7.2.2

History records are smaller and more efficient, because empty properties are no longer included in the snapshot. However, as a result, the history snapshot for sections might present a distorted view of the section.

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)

Pulse Extension points are deprecated

Valid from Pega Version 7.3

Beginning with Pega® Platform 7.3, Pulse uses the notifications feature to send notifications. As a result, Pulse extension points for email body, subject, and recipient list have been deprecated. Preferences set for Pulse notifications in earlier versions are no longer valid.

Use the alternatives listed in the following table to configure your Pulse message and notification preferences.

Deprecated extension pointAlternative extension pointCorresponding notification rule
pyInstantPulseNotification (Correspondence)pyAddPulsePost (Correspondence)pyAddPulsePost
pyReplyPulseNotification (Correspondence)pyAddPulsePost (Correspondence)pyAddPulsePost
pyMentionsPulseNotification (Correspondence)pyAddUserMentionedPost (Correspondence)pyAddUserMentionedPost
pyMentionsInNonCaseContext (Correspondence)pyAddUserMentionedPost (Correspondence)pyAddUserMentionedPost
pyNewPulsePostSubject (Field Value)pyAddPulsePostEmailSubject (Field Value)pyAddPulsePost
pyNewPulseFilePostSubject (Field Value)pyAddPulsePostEmailSubject (Field Value)pyAddPulsePost
pyNewPulseReplySubject (Field Value)pyAddPulsePostEmailSubject (Field Value)pyAddPulsePost
pyMentionedUserSubject (Field Value)pyAddUserMentionedPostEmailSubject (Field Value)pyAddUserMentionedPost
pyMentionedFollowerSubject (Field Value)pyAddUserMentionedPostEmailSubject (Field Value)pyAddUserMentionedPost
pyMentionedFollowerWithFilePostSubject (Field Value)pyAddUserMentionedPostEmailSubject (Field Value)pyAddUserMentionedPost
pyGetListOfEmailReceivers (Activity)D_pxGetCaseFollowers (Data page)pyAddPulsePost

To continue using the deprecated extension points, override the pyInvokepxNotify when rule and set it to return false.

For more information, see Management of user notification preferences.

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.

Deprecated survey APIs

Valid from Pega Version 7.3

APIs that were available in the PegaSurvey ruleset have been superseded by Pega® Platform APIs. Although older APIs continue to function in this release, it is recommended that you update your flows and flow actions to use the new APIs because they provide the latest survey capabilities, and deprecated features are not supported.

The following table maps deprecated APIs to their replacement APIs.

Deprecated APINew APIDescription
Work-.QuestionShapeWork-.pzQuestionShapeA flow that displays one simple question.
Work-.QuestionShapeScrWork-.pzQuestionShapeScrA screen flow that displays one simple question.
Work-.SurveyDriverWork-.pxSurveyDriver

A flow that displays questions in a survey, which can be simple or complex.

You can control whether the questions are displayed on one or multiple screens.
Work-.SurveySectionWork-.pxSurveySection

A section that displays questions in a survey.

You can reference this section from a user action, such as a flow action or connector flow action, in a flow.

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