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.

Mobile features deprecated in 8.4

Valid from Pega Version 8.4

Following the introduction of new functionalities for mobile apps, some features are reaching end of life. To avoid additional effort during updates to future releases, do not use deprecated features.

In the 8.4 release, the following features are no longer recommended:

  • Mobile Client 7 is now deprecated and planned for removal in 8.5. Use Pega Infinity Mobile Client to meet the mobile needs of your business.
  • The Reuse existing web portal functionality is deprecated and planned for removal in 8.5. For improved app performance and more efficient development, use the mobile app builder in the mobile channel. Also, you must convert existing projects to use separate channels for mobile and web portals before upgrading to 8.5.

In addition, the Pega Mobile Express app has been removed from app stores and replaced with the Pega Mobile Preview app.

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.

Source field not displaying in data transform

Valid from Pega Version 7.1.4

On the Data Transform rule form when using the Update Page action, if the Relation value is updated to “with values from”, the Source field will not be displayed.

(Note that for existing data transforms where the Source field has already been completed, this situation should not occur.)

Workaround

  1. Below is a data transform that has been configured to use Update Page.
    DataTransform1.jpg
  2. If a user were to choose an alternate source by updating the ‘with values from’ Relation value, they would not be prompted to provide a page name in the Source field.
    DataTransform2.jpg
  3. At this point, to be able to enter the Source page value, the user has to save the rule, which results in an error because the source page value is blank. This causes the field to appear.
    DataTransform3.jpg
  4. Once the field has appeared, the Source page value can be provided, and the form can be saved successfully.
    DataTransform4.jpg

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.

Slow WebSphere performance on Mac platforms

Valid from Pega Version 7.1.2

Use the following JVM setting to improve WebSphere performance on Mac platforms:

-Djava.net.preferIPv4Stack=true

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.

High number of busy waits when using Oracle SecureFiles

Valid from Pega Version 7.2.1

You might experience a high number of buffer busy waits when using Oracle SecureFiles for BLOB storage. An Oracle buffer busy wait occurs when a session cannot access a database block in the buffer cache, because another session is either reading the block into the buffer or changing the buffer. As a best practice, use Oracle 11.2.0.4 or later, because earlier versions have more problems with SecureFiles. In addition, to minimize the number of busy waits, set the hidden Oracle parameter _securefiles_concurrency_estimate to 50, and partition the table by using a composite range hash partition that is based on the pxCreateDateTime and pzInskey columns.

For more information, see Troubleshooting: High number of busy waits when using Oracle SecureFiles.

Email approval and instantiation not supported on multitenant systems

Valid from Pega Version 7.2.1

The Enable email approval check box appears on the General tab of an approval step in Case Designer in multitenant systems. It also appears on the Approval shape in Designer Studio. In addition, in Designer Studio, the Settings tab in Case Designer displays the option to configure email instantiation. However, because configuring email listeners is not supported on multitenant systems, you cannot enable email approval or email instantiation.

Ignore locale settings requires refresh after server restarts

Valid from Pega Version 7.2.1

The Ignore locale check box in operator preferences is selected to display Designer Studio in U.S. English. After a server restarts, screens initially ignore this setting. When the screen is refreshed or reopened, the screen is rendered as expected.

Flexbox-based dynamic layouts not supported for Android 4.4 and earlier

Valid from Pega Version 7.2.1

Flexbox-based dynamic layouts are not supported in Android 4.4 and earlier. When developing applications to be used on devices running Android 4.4 and earlier, use the inline-block layout mode for dynamic layouts.

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