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.

Required Oracle optimization parameter

Valid from Pega Version 7.1.3

To optimize performance, set the Oracle parameter optimizer_index_cost_adj to a value between 20 and 25. If this value is not set, the system can run exceedingly slowly, potentially blocking users from login.

Synchronized database and application server settings

Valid from Pega Version 7.1.3

Configure your database and application server to use the same time zone and character encoding to avoid conflicts.

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.

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.

User interface distortions in the Predictive Analytics Director portal

Valid from Pega Version 7.1.6

By default, the New Application wizard configures new applications to include UI-Kit-7 in the list of application rulesets. This ruleset causes user interface distortions in the Predictive Analytics Director portal. Applications created in maintenance level updates previous to Pega 7.1.6, and applications 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.

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.

For Microsoft SQL Server deployments, change settings to create data types in Integration Designer

Valid from Pega Version 8.1

For on-premises deployments that use Microsoft SQL Server, set the Pega-Reporting/reporting/useMergeHintForRRquery dynamic system setting to true. If you do not configure this setting, you might not be able to create a new data type in Integration Designer that uses Pega as the system of record. Configure the setting as follows:

  • Owning ruleset: Pega-Reporting
  • Setting purpose: reporting/useMergeHintForRRquery
  • Value: true

For more information about configuring dynamic system settings, see Creating a dynamic system setting.

Data entered in a new harness is lost after a sync operation

Valid from Pega Version 8.1

If you create a case in an offline-enabled application and enter data in a new harness, this data is lost after you click Submit and the sync operation takes place. For more information, see Offline capability and Enabling offline support for cases.

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