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.

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. 

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.

Update Existing Applications wizard will run for every upgrade

Valid from Pega Version 7.1.7

The upgrade process from a PRPC 5.x or 6.x system to Pega 7.1.7 now automatically runs the Update Existing Applications wizard. This may extend the time that the upgrade process takes to complete, depending on the version you are upgrading from and the number of rules in your application.

Upgrading to Pega 7.1.7 with an Oracle database requires new role permissions

Valid from Pega Version 7.1.7

When upgrading or updating from a prior version to Pega 7.1.7, if your system uses an Oracle database, an additional role is required to support the Reversability functionality. In addition to the Oracle privileges specified in the Install Guides, the role SELECT_CATALOG_ROLE is required. Verify that this role is present before beginning the upgrade or update.

Action required by admins for improved search

Valid from Pega Version 7.1.7

Starting November 13, 2014, after updating to or upgrading from a prior version to Pega 7.1.7, your system administrator must manually build all indexes for Elasticsearch before the system can automatically switch from Lucene to Elasticsearch.

It is recommended that you begin this manual re-indexing process for all enabled index types as soon as your update or upgrade is complete. The search landing page refers to Elasticsearch settings; during re-indexing, however, Lucene search continues to function to ensure that there is no interruption in search functions. When planning the re-indexing, be aware that the initial re-indexing requires significant resources on the host node and can be a lengthy process, depending on the number of rules and work objects in your system.

See the Pega 7.1.7 Upgrade Guide for information about manually indexing Elasticsearch.

Run cleanup.bat/sh script only before upgrading

Valid from Pega Version 7.1.1

Prior to upgrading the rulebase, you can optionally run the cleanup.bat/sh script to remove older rules from the database.

Run this script before you upgrade your rulebase, or the script may delete needed rulesets. For more information about running the cleanup.bat/sh script, refer to the Upgrade Guide specific to your release version.

Updates no longer require redeploying the prweb.war file or the application server-specific EAR file

Valid from Pega Version 7.1.7

Updating from Pega 7.1.7 to later versions of Pega 7 no longer requires that you redeploy the prweb.war file or the application server-specific EAR file.

Note that upgrades from versions prior to Pega 7.1.7 still require that you redeploy these files.

End of support for Microsoft Internet Explorer 9 and Internet Explorer 10

Valid from Pega Version 7.2

In accordance with Microsoft’s announcement to discontinue support for Internet Explorer 9 and Internet Explorer 10 in January 2016, Pega 7.2 will be the last version of the Pega 7 Platform to support Internet Explorer 9 and Internet Explorer 10.  

For Pega 7.2.1, you must upgrade to Microsoft Internet Explorer 11 or later, or use Google Chrome, Apple Safari, or Mozilla Firefox.

For more information about browser support, see the Platform Support Guide or contact Pegasystems Global Customer Support.

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