Published Release Notes

Rollback functionality is limited to latest revision

The rollback functionality in DSM Revision Manager allows customers to roll back the import of the latest revision to their DSM application. Only one rollback is allowed; after a rollback, the rollback option is disabled until the next revision is imported. If importing two (or more) revisions at once then attempting a rollback, the system only rolls back one revision.

Example: a user has a base DSM application. They import Revision 1, and then import Revision 2. Next, they try to roll back both revisions. The system reverts to the Revision 1 version of the application, and the customer cannot revert all the way back to the base application.

System Management Application displaying listeners that do not require any action

After installing or upgrading to Pega 7.1.7, there is an additional available listener (Data-Decision-DNode-Service:Default) that does not require any action. This listener can be safely ignored and you should not use the System Management Application to manage any of its operations or state.

• The Data-Decision-DNode-Service:Default listener is always running on every PRPC node.
• The state of this listener is internally managed by PRPC. Starting or stopping it through SMA does not have any effect on its state.

Open ports required for cluster communication

In a Pega 7 system, there can be multiple servers, or nodes, and each node can contain multiple JVMs.  In Pega 7.1.7, the port range 5701-5800 needs to be left open for cluster communication.   The number of available ports in this range needs to be greater than or equal to the greatest number of JVMs on any one node in the cluster.  So for example, if there are 3 JVMs on one node, and 7 JVMs on another node, there need to be at least 7 ports available.  By default, the system will begin with port 5701, and then look for the next port in the sequence (5702, followed by 5703).

If these ports are not available, you will see the following error:

ERROR   - PegaRULES initialization failed. Server: ABCDEF123

com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed

< . . . Java dump here . . . >

Caused by: com.hazelcast.core.HazelcastException: ServerSocket bind has failed. Hazelcast cannot start! config-port: <port>, latest-port: <port>

Recommended heap sizes

The heap is a storage area in the Java virtual machine (JVM) allocated for both short-term and long-term (shared) object storage. If the server does not have enough memory allocated to run Pega 7, the system can hang without an error message. If this occurs, your values need to be higher than the recommendations based on your server hardware and the number of other applications on the server.

Pegasystems recommends using these settings:

• Initial Heap Size (Xms): 1 GB
• Maximum Heap Size (Xmx): 12 GB (8 GB minimum)

If your application server is using the Oracle JVM, also add the PermSize and MaxPermSize settings:

• PermSize (-XX:PermSize): at least 256MB
• MaxPermSize (-XX:MaxPermSize): at least 512MB

Set the JVM memory options to increase the amount of system memory allocated to the application server running Pega 7 by selecting Designer Studio > System > Operations > System Management Application and then selecting a listed node.

See the Pega 7.1.7 Installation Guides for more information about how to make these setting changes.

Cannot create new data tables after update

Data tables have been replaced by a new local data storage format. You can upgrade old-style data tables to use the new local data storage format, but the new format is not compatible with earlier versions of Pega 7 in which data tables could be created.

You can still edit legacy data tables by using the old data table functionality. However, to create new data tables, you must use the Data Explorer and Data Designer.

The System Management Application is supported only on Microsoft Internet Explorer

Microsoft Internet Explorer (IE) is required for the System Management Application (SMA). No other browser is supported.

Create and modify tenants only from the Tenant Management landing pages or SOAP operations

When creating or modifying tenants, do not use any of the following methods:

• Creating a new tenant definition from the Data-Admin-Tenant list
• Using the Save As feature to create a tenant from an existing tenant
• Creating a tenant from the rule form from the Action > Create menu

Although these methods might appear to work, the resulting tenants have no associated metadata and are not valid. Always use landing pages or SOAP operations to create or modify tenants.

Work attachment indexing fails with IBM SDK Java 6

Indexing of work attachments fails when you use IBM SDK Java 6 with Pega 7.1.7 through Pega 7.2. The workaround is to switch to IBM SDK Java 7 or Oracle JDK Java 1.6. You can also disable attachment indexing from the Search landing page; however, if you do this, you are not be able to search the content of attachments.

End of active support for Cosmos React version 8.6

As of the release of Pega Platform™ version 8.8 in October 2022, the early adopter Cosmos React (now Constellation) UI is no longer supported. Consequently, Pega support teams no longer accept assignments and incident reports for the 8.6 version of Cosmos React and DX SDK. Upgrade to a later version of Cosmos React or Constellation to maintain support.