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.

Both Transfer and Transfer Assignment flow actions are displayed in the Bulk Actions tool

Valid from Pega Version 7.1.7

Both the deprecated Transfer flow action and its Pega 7.1.7 replacement Transfer Assignment (pyTransferAssignment) might appear in the Select Action menu on the Bulk Actions tool.

Either of the following situations can cause this behavior:

  • The original application did not contain the UI-Kit-7 ruleset, for example, the application was built on Pega 7.1.5.
    • The default flow actions are based on BulkProcessTransferFlowAction system settings.
    • If you add pyTransferAssignment as a local action in a case type rule, users will see both old and new actions.
    • The flow actions are still available unless you override the settings.
  • The upgraded application uses the UI Kit ruleset, but the Transfer local action was defined in the original case type rule and copied to the application.
    • The original is explicitly defined in the application.
    • pyTransferAssignment is available through the system settings in the UI Kit.

As a best practice, upgrade Transfer flow actions to Transfer Assignment in your flows and local actions. The UI Kit ruleset ensures that the new flow actions are optimized for mobile interfaces. In addition, Transfer Assignment provides multiple transfer functions (to manager, workbasket, advanced options) in a single form.

Alternatively, keep the original system settings so that the existing flow actions are still available.

Offline mobile apps require Dynamic Container to use frameless Single Document mode

Valid from Pega Version 7.1.7

You can add a Dynamic Container (DC) directly into a Dynamic Layout cell. When creating a custom mobile app with offline capability, you must use the frameless Single Document mode of DC.

Note that mobile offline capability does not support using a framed Single Document mode.

Flow import functionality is limited to Microsoft Internet Explorer Version 9 and Version 10 in Pegasystems Public Format

Valid from Pega Version 7.1.7

Importing a flow in the Rule-from-File wizard is limited to Microsoft Internet Explorer 9 and Internet Explorer 10 in the Pegasystems Public Format .

No support for Android versions earlier than 4.4 on mobile devices

Valid from Pega Version 7.3

Pega® Platform dynamic layouts by default now use Flexbox-based rendering. As a result, mobile devices running on Android versions earlier than 4.4 are not supported in Pega Platform. Such devices cannot render correctly with Flexbox because the Pega Mobile Client includes the default stock browser on the Android operating system.

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.

Package caching is not supported in offline-enabled applications built with the UI Kit 7 (09-01-01) portal

Valid from Pega Version 7.3

When you create an offline-enabled application in Pega® Platform, by default, it uses a portal with the UI Kit 7 (09-01-01) ruleset. In such a case, the package caching functionality cannot be used. You must either disable caching on the Advanced tab of the Access Group rule form, in the Offline Configuration section, or use an adaptive design instead of rendering different elements for different devices with the UI Kit 7 (09-01-01) ruleset.

For more information, see Access Group form - Completing the Advanced tab.

No video controllers displayed on Android 4.3 and earlier versions

Valid from Pega Version 7.3

When you preview a video clip within Pega® Mobile Client on a mobile device that runs Android 4.3 or earlier versions, video controllers are not displayed in full-screen mode.

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