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.

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.

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.

Context-specific documentation is not available in express mode

Valid from Pega Version 7.1.9

Help topics that are opened from express mode display content that is specific to Designer Studio.

If your system is dedicated to applications that are developed in express mode exclusively, and you do not need Designer Studio help topics, you can set the Online Help URL field on the System Settings landing page to: https://pdn.pega.com/sites/default/files/help_p7e/procomhelpmain.htm. Alternatively, you can view the contextual help system for Pega 7 Express in a separate browser tab.

Design-time limitations in express mode

Valid from Pega Version 7.1.9

Some limitations apply when you develop an enterprise application in express mode. At design time, some features are disabled or have limited options when you configure them in Designer Studio and switch to express mode. The use of these features does not restrict the run-time behavior of your application; however, you cannot change the configuration of these features unless you switch from express mode to Designer Studio.

For more information about each limitation and the recommended action to take, see the following information:

Problem with truncating Decision Data Store data set

Valid from Pega Version 7.1.9

The Truncate operation for the Decision Data Store data set may cause timeout exceptions. This problem is caused by the Apache Cassandra database that waits until compaction tasks finish before it can truncate the data set.

Recommendation:

Repeat the Truncate operation until it is successful.

Node description cannot match application server node name

Valid from Pega Version 6.3 SP1

A node's Short Description should not be the same value as the application server node name. If the node's Short Description is changed to be the same value as the application server node name, then the node description is automatically changed back to the original value after a system restart.

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.

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