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.

Limits on active data flow runs

Valid from Pega Version 8.5

You can now configure a maximum number of concurrent active data flow runs for a node type. Set limits to ensure that you do not run out of system resources and that you have a reasonable processing throughput. If a limit is reached, the system queues subsequent runs and waits for active runs to stop or finish before queued runs can be initiated, starting with the oldest.

For more information see, Limit the number of active runs in data flow services (8.5).

Upgrade impact

If you have many data flow runs active at the same time, you might notice that some of the runs are queued and waiting to be executed.

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

You do not have to take any action. After the active runs stop or finish, the queued runs start automatically. The default limits are intended to protect your system resources, and you should not see a negative impact on the processing of data flows. However, if you want to allow a greater number of active data flow runs to be active at the same time, you can change the limits. For more information, see Limiting active data flow runs.

External data flow rules are deprecated

Valid from Pega Version 8.5

External data flows are now deprecated and no longer supported. To improve your user experience with Pega Platform™, the user interface elements associated with these rules are hidden from view by default. Identifying unused features allows Pega to focus on developing and supporting the features that you need.

For more information, see Deprecated: External data flows.

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.

Visual Business Director data is automatically cleaned after a retention period expires

Valid from Pega Version 8.5

To avoid negative impact on system resources, such as memory and disk space, Pega Platform™ automatically cleans out collections data accumulated in Visual Business Director after the time period specified in the vbd/dataRetentionTimeout dynamic system setting.

Upgrade impact

In versions of Pega Platform earlier than 8.5, collections data was not automatically removed. From version 8.5, the data is removed after 465 days (15 months) by default.

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

If the default data retention period does not meet your requirements, you can change it by editing the vbd/dataRetentionTimeout setting.

For more information, see "Configuring the data retention period for Visual Business Director" in the Pega Customer Decision Hub 8.5 Upgrade Guide on the Pega Customer Decision Hub product page.

Uploading customer responses into adaptive models is no longer available

Valid from Pega Version 8.5

The option to train adaptive models by uploading a static list of historical interaction records has been deprecated in Pega Platform™ 8.5.

Upgrade impact

In versions of Pega Platform earlier than 8.5, it was possible to train an adaptive model by uploading historical data of customer interaction. After the upgrade to version 8.5, this option is no longer available.

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

Use data from a report definition to train adaptive models. For more information, see Training adaptive models.

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.

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.

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.

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