Published Release Notes

Improved case auditing in App Studio

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.

Tamper-proof Pega Web Mashup loading

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.

Support for validations in Declare Expression rules

Pega Platform™ now correctly evaluates validations on target properties in Declare Expression rules. As a result, any validations defined on properties that have Declare Expression rules in previous releases, now work correctly. 

Upgrade impact

Any unintended validations on properties that have configured Declare Expression rules, both default and user-defined, might cause issues in an application upon saving work objects and data objects that refer to Declare Expression rules.

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

If you experience issues when saving objects, debug your application by setting the declareexp/target/validation/disable dynamic system setting to true. If your application works correctly after the change, it means that validations on Declare Expressions cause the issues. For your application to work correctly, analyze the log files and remove any unintended validations.

For more information, see Declare Expression rules.

Limited access for end user portals

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

• WorkUser
• WorkManager

Nesting dynamic containers not supported

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.

Tags disappear from Rich Text Editor source mode

When you use Rich Text Editor in HTML source mode, some tags disappear from the markup, which causes backward compatibility issues and data loss.

Cause

Pega Platform™ version 8.5.5 introduced the DOM Purifier security plugin. The plugin removes potentially vulnerable tags, including custom tags, from the raw HTML code in the Rich Text Editor source mode.

Workaround

You can disable the DOM Purifier plugin by adding the the window.disableDomPurifier = true markup to the userWorkForm HTML fragment rule.

Alternatively, as of Pega Platform version 8.5.6, you can add a tag to the allow list by including the window.rteCustomAllowedTags = ['myCustomTag'] snippet in the userWorkForm HTML fragment rule. 

In Pega Platform versions 8.5.6 to 8.6, the iframe tag is added to the allow list by default.