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.
Automated Unit Testing is unavailable
Valid from Pega Version 7.1.1
Automated Unit Testing (AUT) is unavailable in 7.1.1 - 7.1.5.
Starting in 7.1.6, users can access AUT features from supported browser versions of IE.
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.
Deprecated end user portals
Valid from Pega Version 7.1.1
The following portals are no longer be supported:
- SysAdmDD
- WorkUserDD
- WorkManagerDD
As a best practice, customize standard, supported portals rather than update your existing portals to include new features.
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:
- Wait approximately eight minutes for the file to import.
- Close and restart the wizard.
- Click Next to skip the upload step.
- Select the name of your file from the list of import files.
- 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:
- 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.