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.

Change logic does not work in Report Editor

Valid from Pega Version 7.1.2

The Report Editor​ change logic button does not work. As a workaround, use the rule form to change the logic.

Geolocation tracking requires browser permission

Valid from Pega Version 7.1.6

When the geolocation tracking feature is enabled, a Map it link appears next to each requestor entry in the audit trail. When you click a link for the first time, the browser displays a notification asking whether you want to permit tracking. Make your yes/no selection in the prompt. Do not click "X" to close it, as doing so may render the session unresponsive. Refresh the browser if necessary and make your selection.

Geolocation tracking Map it links do not appear

Valid from Pega Version 7.1.6

If geolocation tracking is enabled, the first time you create a case in the first browser session, the Map it links do not appear next to the initial audit trail entries. When you submit the first flow action, the links appear next to all subsequent entries.

Use fast processing option does not work

Valid from Pega Version 7.3.1

The Use fast processing option on Connect REST and Service REST rule forms does not work unless you obtain the HFix-43000 hotfix from Global Customer Service.

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