Additional upgrade scripts for new columns
Valid from Pega Version 7.1.4
In Version 6.2, additional columns (Major, Minor, and Patch) containing ruleset Version information were added to 15 tables in the PRPC database. When upgrading from a pre-Pega 7 release, scripts must be manually run after the upgrade to populate these columns.
These scripts are located in the Resource Kit, under Additional Upgrade Scripts.
- If upgrading to a single schema, run both scripts.
- If upgrading to a split schema, run the _data script against the data schema and run the _rules script against the rules schema.
Choose the scripts for your database type:
- db2zos_rulesetversion_columns_data.sql
- db2zos_rulesetversion_columns_rules.sql
- mssql_rulesetversion_columns_data.sql
- mssql_rulesetversion_columns_rules.sql
- oracle_rulesetversion_columns_data.sql
- oracle_rulesetversion_columns_rules.sql
- postgres_rulesetversion_columns_data.sql
- postgres_rulesetversion_columns_rules.sql
- udb_rulesetversion_columns_data.sql
- udb_rulesetversion_columns_rules.sql
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.
Support for character data type on local variables in activities deprecated
Valid from Pega Version 8.1
Support for the character data type for local variables in activities is deprecated. Use the string data type instead.
For more information about activities, see Activities.
When rule might not resolve against @baseclass
Valid from Pega Version 8.1
In the rare case in which a step page context is null, or the pxObjClass associated with the step page is empty, the system no longer attempts to resolve the when rule against @baseclass. As a result, you might see more rule not found errors. Check the step page context and class and ensure that they are not null or empty. In all other cases, if a when rule is not found in any other part of the class hierarchy, the system attempts to resolve it against @baseclass.
DCO Compatibility tool is deprecated
Valid from Pega Version 8.1
The DCO Compatibility tool has been deprecated. Use the Application Guardrails landing page to see the compliance score and any warnings for your application.
For more information, see Application Guardrails landing page.
Apache Ignite is no longer supported
Valid from Pega Version 8.1
Apache Ignite is no longer supported and has been replaced by Hazelcast Enterprise Edition 3.10 in embedded mode. If you used encryption with Apache Ignite, you can configure encryption on Hazelcast Enterprise Edition in the same way that you configured it for Apache Ignite.
For more information about encrypting nodes, see Enabling encrypted communication between nodes.
@java and locatable pages no longer supported
Valid from Pega Version 8.1
@java and locatable pages are no longer supported. Existing rules that use @java and locatable pages will continue to work; however, changes to these rules cannot be saved unless @java and locatable pages are replaced by supported functionality. Use a rule utility function (RUF) instead of an @java page, and use a data page instead of a locatable page. In addition, Pega Platform™ displays a guardrail warning when you open a rule that uses an @java page or a locatable page.
Search indexes require rebuilding after upgrading from Pega Platform 7.1.7 through 7.2.1
Valid from Pega Version 8.1
Pega Platform™ now supports Elasticsearch 5.6.9. If you are upgrading from Pega 7.1.7 through 7.2.1, discard your existing indexes and build new indexes in a new empty index directory. Create the search indexes by using the Search landing page or the full text indexer. If you are upgrading from Pega Platform 7.2.2 or later, no action is required. You can continue to use your existing search indexes.
For more information, see Rebuilding search indexes and Batch creation and updating of Elasticsearch index files from the command line.
Authentication profile for Connect REST might be removed after upgrade
Valid from Pega Version 8.1
The Use authentication check box has been removed from the Service tab on the Connect REST form. As a result, after an upgrade, the Authentication profile field might be blank even if an authentication profile was previously configured.
- If the Use authentication check box was cleared prior to upgrading and the Authentication profile field was configured with an authentication profile name, the Authentication profile field is blank. If you are using authentication, you must reenter the profile name.
- If the Use authentication check box was selected prior to upgrading and the Authentication profile field was configured with an authentication profile name, the Authentication profile field retains the previous configuration.