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.
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.
Privilege required for Recent Explorer
Valid from Pega Version 7.1.1
Users with custom roles defined must add the pxUpdateRecents privilege to see work in the Recent Items Explorer.
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:
- Stop the system.
- Rename one table (“TableX”) to backup (“TableXBackup”).
- Create a new table space that uses a 32K page size.
- Copy “TableXBackup” to “TableX” in the new table space.
- Restart the system and test to verify there are no issues.
- 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.
Use standard Developer portal
Valid from Pega Version 7.1.1
Customized versions of the Developer portal rely on legacy components and are not supported.
To avoid backwards compatibility issues, update your access group to point to the standard Developer portal prior to upgrade.
Top-level (named) pages may no longer be classless
Valid from Pega Version 7.1.1
Newly created top-level (named) pages may no longer be classless or have a blank pxObjClass property. This change can affect applications upgrading from versions prior to Pega 7 to the latest version, especially when:
- Application logic relies on a blank value in the pxObjClass property.
- An activity assumes a new top-level page is classless and explicitly sets pxObjClass in a Property-Set step.
- A data transform assumes a new top-level page is classless and explicitly sets pxObjClass using a Set action.
To avoid application failures, remove or update any logic that expects a blank pxObjClass. Where possible, use the new engine API that finds a page by both name and class:
findPageWithException(PageName, ClassName);
Activities and data transforms continue to create a top-level page when one does not exist. The class name is now derived from the Pages and Classes tab.
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:
- Identify all custom requestor rules (browser, batch, app, portal) with access groups that point to prior versions of PRPC.
- 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.
- Reset your system name to its original value. You can set the Dynamic System Setting prconfig/identification/systemName/default or use the landing page.
- Restart the system.
DB2-LUW database logfile size increase
Valid from Pega Version 7.1.5
To avoid running out of logfile space due to large transaction sets during the rule base load of a Pega 7.1.x install, upgrade, or maintenance level update, systems supported by a DB2-LUW database platform should increase the LOGFILSIZ parameter to at least 4096 pages from the default size of 1000 pages.
After the size has been increased, restart the database to ensure that the new setting is loaded into the database correctly.
Need to run script before updating Multitenant systems
Valid from Pega Version 7.1.5
When updating or upgrading a Multitenant system from Pega 7.1.5 or 7.1.6 to Pega 7.1.7, if that system uses either an Oracle or a PostgreSQL database, you may encounter the error:
“Table must be empty to add column.”
The Multitenant architecture requires an additional column on a number of the PRPC database tables (“pzTenantID”). In Pega 7.1.7, two additional PRPC tables were tenant-qualified: pc_schedule_task and pr_index_schedule_task. The Multitenant column is added to these tables by the update/upgrade process. However, Oracle and PostgreSQL do not allow the addition of a non-null column to an existing table unless the table is empty, so updating or upgrading systems on those databases displays the error detailed above.
To avoid this error, before beginning the update or upgrade, it is necessary to run a script:
- Oracle —
OracleMTupgrade.sql
- PostgreSQL —
PostgresMTupgrade.sql
For updates, these scripts are located in the /scripts/ddl
directory.
For upgrades, these scripts are located in the /Resourcekit/AdditionalUpgradeScripts
directory.