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.

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.
  Depending upon your database type (platform) and the size of your database, these scripts may require significant time and system resources to run.

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

This issue applies to DB2-LUW database platforms only.
 

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:

  • OracleOracleMTupgrade.sql
  • PostgreSQLPostgresMTupgrade.sql

For updates, these scripts are located in the /scripts/ddl directory.

For upgrades, these scripts are located in the /Resourcekit/AdditionalUpgradeScripts directory.

Discontinued support for list view and summary view rules

Valid from Pega Version 7.2

The list view rule and the summary view rule are deprecated, and support for these rules has been discontinued. Existing list view and summary view reports will continue to work on supported browsers. However, the last version of Internet Explorer that list view and summary view rules support is Internet Explorer 11.

You cannot create new list view or summary view reports. Instead, create list reports and summarized reports by using the report definition rule. To prevent display issues, re-create the custom list view and summary view reports that you need as report definition reports.

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.

Unused agents run in background

Valid from Pega Version 7.2

The Update PegaRULES database table statistics agent and the Collect PegaRULES database blob size statistics agent have been added to support future development. These agents run in the background, but they do not do anything. You can, but do not need to, disable them from the Edit Agent Schedule landing page.

For more information, see Agent Schedule form - Completing the Schedule tab.

No longer supported translator configuration options

Valid from Pega Version 7.4

The following translator configuration options are not needed and are no longer supported. If you previously configured any of these system settings, remove them from the system settings to avoid a warning message. For example, if you set translator/useparserfamily, the following message is displayed at startup: "Translator option, 'translator/useparserfamily' is not needed and no longer supported. Remove this from the system settings."

  • translator/useparserfamily
  • translator/usecodegenerator
  • translator/usenativedouble
  • translator/optimization/use71BlockAnalysis
  • translator/optimization/use71ConstantFolding
  • translator/optimization/use71AssignmentTypeSimplification
  • translator/optimization/use71IntrinsicFunctions
  • translator/use71PropSetGeneration
  • translator/use71ParserAssignment
  • assembly/model/useBlock4ContiguousSets
  • /translator/pandc/comparepandcalgorithms
  • /translator/pandc/use6xalgorithms
  • /Compatibility/CheckForTopLevelClassMismatch

In addition, the com.pega.pegarules.generation.parseoverride bootstrap option is no longer supported. Remove this option from the system settings.

PegaDATA connection settings now required in the prconfig.xml file

Valid from Pega Version 7.4

If you use the default prconfig.xml file that is included with Pega® Platform, and you have not removed the PegaDATA connection settings, no action is required. If you use a custom prconfig.xml file, for example, for running tests, ensure that the database connection settings for PegaDATA are not blank.

For more information about the connection settings, see PegaDATA connection settings in the prconfig.xml file.

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.

New roles required for system management features and APIs after upgrade

Valid from Pega Version 8.1

The pzSystemOperationsObserver and pzSystemOperationsAdministator privileges are no longer used for accessing system management features in Admin Studio and for system management APIs. Pega Platform™ has new privileges for individual system management functions and new roles configured with these privileges. Use the following roles to access system management features and APIs:

  • PegaRULES:SysOpsAdministrator – has all administrator and observer privileges
  • PegaRULES:SysOpsObserver – has all observer privileges
  • PegaRULES:SysAdm4 – has all administrator and observer privileges

After upgrading, you can include one or more of these roles in your access group or create a custom role. For more information about access roles, see Access roles.

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