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.

Flow rules not supported in IE8

Valid from Pega Version 7.1.1

In versions prior to 7.1.2, flow rules do not open in Internet Explorer 8 (IE8). Upgrade your system to the latest version of PRPC or access flows from another supported browser.

Supported JDBC drivers

Valid from Pega Version 7.1.1

Pega 7.1.1 supports Java 6 and Java 7 SDKs only. Ensure that the JDBC driver you are using supports those versions of Java. See your database installation or upgrade documentation for additional information.

DatabaseJava 6Java 7
Oracleojdbc6.jarojdbc7.jar
MSQLsqljdbc4.jarsqljdbc4.jar
DB2 LUWdb2jcc4.jardb2jcc4.jar
DB2 z/OS*db2jcc4.jar or jdb2jcc.jar**db2jcc4.jar
PostgreSQLpostgresql-9.1-903.jdbc4.jar***postgresql-9.1-903.jdbc4.jar

* JDBC drivers are only available from the DB2 for z/OS product. Additionally, you need db2jcc_license_cisuz.jar in the same directory as db2jcc4.jar.

** The db2jcc.jar has been deprecated and may not be supported in future releases.

*** This .jar file is required for PostgreSQL version 9.1.x.

Turn off saved connections in WebLogic

Valid from Pega Version 7.1.1

PRPC caches connections in thread-local storage. When using a WebLogic application server, set database/savedconnections to FALSE to avoid incorrectly saved, container-managed transactions. You can make this update through JNDI settings or by adding an entry to the prconfig.xml, for example:

<env name="database/savedconnections" value="false" />

Remove JVM settings from prior installations

Valid from Pega Version 7.1.1

JVM memory settings ​defined in the setupDatabase.properties file to support a prior installation need to be removed. 

Memory settings are now handled by the installation program. Duplicating these settings may cause installation or upgrade failures. 

IE8 hangs on large imports

Valid from Pega Version 7.1.1

IE8 users may experience a hung process when running the Designer Studio > Application > Distribution > Import wizard. This issue is related to low-capacity networks and large (300+ MB) archive files.

Although the processing symbol prevents you from proceeding to the next step in the wizard, the file is still imported to the server. As a workaround, you can:

  1. Wait approximately eight minutes for the file to import.
  2. Close and restart the wizard.
  3. Click Next to skip the upload step.
  4. Select the name of your file from the list of import files.
  5. Complete the remaining steps in the wizard.

Required DB2 settings for LUW and z/OS

Valid from Pega Version 7.1.1

Installations on DB2 databases for LUW and z/OS require a minimum logging file size (4096) and a default table space page size (32K).

To set the table space page size to 32K:

  1. Stop the system.
  2. Rename one table (“TableX”) to backup (“TableXBackup”).
  3. Create a new table space that uses a 32K page size.
  4. Copy “TableXBackup” to “TableX” in the new table space.
  5. Restart the system and test to verify there are no issues.
  6. Drop the backup table (or keep it for future reference).

Additional information is available in the "Adjusting the log space size in upgraded databases" article: https://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=%2Fcom.ibm.db2.luw.qb.upgrade.doc%2Fdoc%2Ft0023289.html

No direct upgrade to multitenant setup

Valid from Pega Version 7.1.1

It is not possible to upgrade directly to a multi-tenant setup. A Pega 7 application may be exported and then imported into a multi-tenant system, with the administrator making the decision as to whether this then becomes a tenant system or a shared system.

 

Applications developed in versions prior to Pega 7 must be upgraded to a Pega 7 standard system, and then exported and imported into a multi-tenant system. See the Multitenancy Administration Guide for full details.

Upgrade changes system name

Valid from Pega Version 7.1.1

As of Pega 7.1.7, the following renaming behavior no longer occurs.

The upgrade process renames your system to “PRPC” and modifies any custom requestor rules in your application to use this name. After the upgrade completes, you must apply these changes to revert your system:

  1. Identify all custom requestor rules (browser, batch, app, portal) with access groups that point to prior versions of PRPC.
  2. Open the relevant access groups (for example, PRPC:Unauthenticated and PRPC:Agents) and update the name and version fields to point to the current PegaRULES application.
  3. Reset your system name to its original value. You can set the Dynamic System Setting prconfig/identification/systemName/default or use the Designer Studio > System > Settings > System Name landing page.
  4. Restart the system.

Required DB2 settings

Valid from Pega Version 7.1.1

For customers using the DB2 Version 4 drivers (“db2jcc4.jar”), it is necessary to set the custom connection property useJDBC4ColumnNameAndLabelSemantics to “false”.   

For customers using DB2 with WebSphere, the useJDBC4ColumnNameAndLabelSemantics property in the DB2 data source needs to be changed from a Boolean to an Integer and set to "2". 

EAR support for JBoss EAP 6

Valid from Pega Version 7.1.5

PRPC deployment in JBoss EAP 6 as an EAR archive is now supported. 

If you need to deploy the JBoss EAR file, go to My Support Portal and submit a Support Request. GCS can assist you with the procedure.

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