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.

Automated Unit Testing is unavailable

Valid from Pega Version 7.1.1

Automated Unit Testing (AUT) is unavailable in 7.1.1 - 7.1.5.

Starting in 7.1.6, users can access AUT features from supported browser versions of IE.

IE8 limits expansion features

Valid from Pega Version 7.1.1

Internet Explorer 8 (IE8) does not support CSS media queries, which are used by re-expansion features in the Designer Studio. IE8 users with low screen resolution (800 x 600) and a small window size may find that the explorer area in the Designer Studio collapses but cannot re-expand. 

As a work around, access the Designer Studio from another supported browser version and use the recommended, minimum screen resolution width of 1280 pixels.

Limited access for end user portals

Valid from Pega Version 7.1.1

The following portals are only accessible from supported versions of Internet Explorer in “quirks” mode:

  • WorkUser
  • WorkManager

Nesting dynamic containers not supported

Valid from Pega Version 7.1.1

Do not include a section containing a dynamic container inside of another dynamic container. This configuration may cause performance issues resulting in unexpected behavior at runtime, and is not supported.

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.

ShowWarningOnForm is no longer processed

Valid from Pega Version 7.1.7

Rule forms now display all warnings, independent of category or type. The standard decision tree Embed-Warning.ShowWarningOnForm is no longer used to determine which warnings are visible.

You can safely remove any specialized versions of this rule in your application.

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 .

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.

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