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.

Stages and Steps may not appear as expected

Valid from Pega Version 7.1.5

There are some unique configurations of the newly enhanced pxDisplayStages gadget that can lead to case type "Stages and Steps" appearing more than once or not at all.  In the event that your application experiences one of these scenarios, the recommended work around is to relocate the gadget:

  • Add pxDisplayStages to the pyCaseContainer section (or equivalent)
  • Remove pxDisplayStages from the pyCaseActionArea section (or equivalent).

Geolocation tracking requires browser permission

Valid from Pega Version 7.1.6

When the geolocation tracking feature is enabled, a Map it link appears next to each requestor entry in the audit trail. When you click a link for the first time, the browser displays a notification asking whether you want to permit tracking. Make your yes/no selection in the prompt. Do not click "X" to close it, as doing so may render the session unresponsive. Refresh the browser if necessary and make your selection.

Geolocation tracking Map it links do not appear

Valid from Pega Version 7.1.6

If geolocation tracking is enabled, the first time you create a case in the first browser session, the Map it links do not appear next to the initial audit trail entries. When you submit the first flow action, the links appear next to all subsequent entries.

User interface distortions in the Decision Manager portal

Valid from Pega Version 7.1.6

By default, the New Application wizard in Pega 7.1.6 configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Decision Manager portal. Both applications created in previous maintenance level updates and applications created in Pega 7.1.6 that do not include the UI-Kit-7 dependency are not impacted by this known issue.

Workaround:

  1. Open the application record.
  2. In Application Rulesets, remove UI-Kit-7.
  3. Save the application record.

User interface distortions in the Predictive Analytics Director portal

Valid from Pega Version 7.1.6

By default, the New Application wizard configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Predictive Analytics Director portal. Applications created in maintenance level updates previous to Pega 7.1.6, and applications that do not include the UI-Kit-7 dependency, are not impacted by this known issue.

Workaround:

  1. Open the application record.
  2. In Application Rulesets, remove UI-Kit-7.
  3. Save the application record.

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.

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.

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