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.

Improved case auditing in App Studio

Valid from Pega Version 8.5

In Cosmos UI, App Studio now supports expandable case steps. This enhancement helps users quickly navigate a case and provides deeper insight into the case flow. In addition, Cosmos UI also introduces an improved history view that helps you better meet your business auditing requirements.

For more information, see Managing Cosmos UI settings in case designer.

Upgrade impact

After an upgrade to Pega Platform 8.5 or later, the history and chevron designs change automatically. However, applications with custom history settings might still display the styling that you defined in the override.

What steps are required to update the application to be compatible with this change?

If your application uses custom settings and you want to use the updated history, remove the overrides from the pyWorkCommonActions rule.

Failed Robotic Assignments work queue type changed to Standard

Valid from Pega Version 8.5

The default Failed Robotic Assignments work queue type is now Standard. In previous releases, the default type was Robotic. For usage information, see Configuring a work queue for robotic automation.

Upgrade impact

After upgrading to Pega Platform 8.5 and later, you cannot save case types in which you configure the Queue for robot smart shape to route new assignments to the Failed Robotic Assignments work queue. Existing assignments that you routed to the Failed Robotic Assignments work queue are not affected.

How do I update my application to be compatible with this change?

As a best practice, do not use the Failed Robotic Assignments work queue in your custom implementations. Instead, configure the Queue for robot smart shape to route new assignments to a Robotic work queue. When possible, update existing case types to use the robotic work queues that you created in your application.

Tamper-proof Pega Web Mashup loading

Valid from Pega Version 8.5

To protect your application from hackers, Pega Web Mashup is now loaded in a more secure way. The system generates a channel ID in the mashup code for validation on the server, before passing the mashup request. 

For more information, see Creating a mashup.

Upgrade impact

After an upgrade to Pega Platform 8.5, existing mashups, which do not have the channel ID parameter in their code, cannot load and users see the access control warning.

What steps are required to update the application to be compatible with this change?

If you need to maintain full availability of the mashup during the upgrade of the production environment, perform the steps in Migrating existing mashups.

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

Cannot copy final section rules in UI Kit ruleset

Valid from Pega Version 7.1.6

You cannot copy section rules in the UI Kit ruleset (UI-Kit-71) that start with pz or px (final rules in the base PRPC rulesets).

Instead, to customize these rules, use the Copy/Merge Ruleset tool, available at Designer Studio >System > Tools > Refactor Rulesets, to copy all rules from the UI Kit into your application ruleset. You can then check the section rules in and out.

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.

Microsof Internet Explorer 9 (IE9) may display a script error when clicking a Help button

Valid from Pega Version 7.1.6

A script error may be displayed when clicking a Help button when script error notification is turned on in the browser. As a work around, uncheck the Display a notification about every script error option in the Advanced tab of the Options dialog box in Microsoft Internet Explorer 9.

Internal rules in search results and explorers

Valid from Pega Version 7.4

Using old: is no longer supported in search. You can include internal rules in search results and make them available in the Application and Records explorers. Include internal rules in search results either by adding the PegaDevelopmentruleset to your application or by clicking the Enable diagnostic features option in your operator preferences.

Browser unresponsive when logging in to Designer Studio

Valid from Pega Version 7.4

The What's new in 7.4 widget on the Designer Studio home page uses WebGL to render its background animation. If your browser is running on a virtual machine without hardware acceleration, your browser might become unresponsive because of this widget. Click the Hide this until next release button to remove the widget. At your next login, the widget will not be displayed.

Applications not working as expected when using fast processing for Connect REST and Service REST integration

Valid from Pega Version 7.4

In Pega® Platform 7.3.1, the Use fast processing option on Connect REST and Service REST rule forms did not work. The functionality has been fixed for Pega 7.4; however, some data model guidelines must be followed. If you use this option in Pega 7.3.1, and you did not follow the guidelines, your application might not work as expected after upgrading. Use the following data model guidelines when using fast processing:

  • The JSON property names and the clipboard property names must match.
  • The JSON tree structure and the clipboard tree structure must be similar.
  • The scalar arrays in JSON must be mapped to the clipboard as page lists.
  • Multi-dimensional arrays must be mapped into page lists of page lists with the same embedded property names.

In addition, page groups, value groups, and Java objects are not supported by fast processing.

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