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.

Database

Valid from Pega Version 7.1.4

Improvements to data handling were made for search indexing, agent processing, and filtering.  Scripts were provided for proper population of the database tables.

 

  • Importing data from shared obj-external tables is now supported.
  • A validation warning will now display when an unexposed property is used in filter or join conditions.
  • A Global Search index may now be created across two databases.
  • Agent processing on multiple nodes has been improved.
  • Improvements were made to controls in Report Definition pages which are used in a dynamic grid.
  • Filtering functionality involving special characters has been enhanced.
  • Scripts have been provided to populate the RuleSetVersion Major, Minor, and Patch columns.

Reporting & Data

Valid from Pega Version 7.1.4

This release fixed many existing unlocalizable elements in 7.1 reporting interfaces (The Report Viewer, Report Editor, Chart Editor, and the Report Browser) and now they are fully localizable. Changes were made to make Listview, summaryview,  and report viewer display possible WCAG 2.0 level A and AA support.

  • Parameters may now be used in a sub-report join condition.
  • Report Definition localization has been enhanced.
  • Standalone ListViews with embedded SmartInfo have been improved to resize appropriately when the SmartInfo section is expanded.
  • The data section of a report will now display in all of the available space when a fixed header option is selected.
  • When localizing a listview with filters, tool tips are translated.

System Management

Valid from Pega Version 7.1.4

Refinements were made to out-of-place upgrade documentation and processes, as well as for how handling is performed for all of the database vendor specific nuances related to a deploying into a split schema environment.

  • A script was created to run the data schema upgrade for z/OS systems.
  • In a split-schema configuration, indexing has been enhanced.
  • The product installer has been enhanced.
  • The stand-alone Static Assembly Utility does not require a password for its process.
  • The UpdateManager tool has been improved.

Use JDBC 4 compliant drivers for better performance

Valid from Pega Version 7.1.7

For better performance, ensure that you are using JDBC 4-compliant drivers.  For more information on supported and non-supported JDBC drivers, please reference the Platform Support Guide.

Use Tomcat 7 for better performance

Valid from Pega Version 7.1.7

For better performance with a Tomcat web server, use Tomcat 7.

Tomcat 6 has a limitation that causes the server to treat the JDBC driver as if it were a JDBC 3-compliant driver, even if the system is using a JDBC 4-compliant driver. Customers using Tomcat will see better performance if they upgrade to Tomcat 7 and use a JDBC 4-compliant driver.

Engine will not start if the incorrect JDBC driver is used

Valid from Pega Version 7.1.7

The engine will not start up if the incorrect JDBC driver is used. The following configurations are unsupported:

  • Using a Multi-tenant Oracle system with one of the Oracle JDBC drivers with issues (see the chart in the Platform Support Guide)
  • Using a Multi-tenant system with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)
  • Using Microsoft SQL Server with a JDBC 3 compliant driver, OR with Tomcat 6 (for more information on using tomcat with Pega 7.1.7, see Use Tomcat 7 for best performance)

When any of these unsupported configurations are encountered, Pega 7 will not start. Before this change, the engine would appear to start up properly, but would encounter issues during other parts of the engine startup or during actual use of the system.

List view and summary view reports might not display in HTML5-compliant browsers

Valid from Pega Version 7.1.7

List view and summary view reports use framesets to provide a view of drill-down reports. HTML5 does not support framesets, so these reports might not display well, or at all, in versions of browsers that are compliant with HTML5.

To prevent display issues, re-create the custom list view and summary view reports that you need as report definition reports. Standard management reports are already available as report definition reports.

As of Pega 7.2, list view and summary view rules are deprecated. For more information, see Discontinued support for list view and summary view rules.

IBM WebSphere Application Server V8: Edit the URL for Enabling System Management Application

Valid from Pega Version 7.1.7

WebSphere 8 does not correctly resolve the URL to enable System Management Application. As a workaround, when you configure the application server, you can do either of these actions:

  • Enter the full URL in the format:
    ​http://hostname:port/prsysmgmt/getnodes.action

  • Set the com.ibm.ws.webcontainer.redirectcontextroot property to true.

Open ports required for cluster communication

Valid from Pega Version 7.1.7

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

Valid from Pega Version 7.1.7

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.

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