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.

Rules can no longer access Pega internal Java packages

Valid from Pega Version 8.4

You can no longer create rules that access Java packages that reference internal APIs (syntax com.pega.platform.*.internal*). This change does not affect rules that access Pega public API packages.

If you encounter issues when running existing rules that reference internal Pega APIs, contact Pega Support.

Upgrade impact

After an upgrade to 8.4 and later, clients can no longer save new or modified rules that access Pega internal APIs; existing rules that reference internal APIs can still be run but cannot be modified. 

What steps are required to update the application to be compatible with this change?

Following a software upgrade to 8.4 or later, clients can refactor existing rules into guardrail compliant rules. To find rules to refactor, run the validation tool from designer studio (Application > Tools > Validation) to identify what rules fail validation; failed rules that include the message "Test compilation failed : Illegal internal class reference : com.pega.internal.XYZ" can updated to reference appropriate APIs.

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

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.

Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3

Valid from Pega Version 7.3

If you used node classification in Pega® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type.

  • UniversalNode becomes Universal
  • WebUserNode becomes WebUser
  • BackgroundProcessingNode becomes BackgroundProcessing
  • BIXNode becomes BIX
  • SearchNode becomes Search

If you created agents in Pega 7.2.2, agent schedules are also automatically updated with a new name during the upgrade. For more information, see Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade and the appropriate Deployment Guide.

Rollover policy for log files

Valid from Pega Version 7.3

The rollover policy for log files is now based on time (daily) and file size (maximum file size is 250 MB). Log files are rolled over daily or when the maximum file size is reached. Current (not rolled over) log files do not have a time stamp. The time stamp is added when the log file is rolled over. In addition, the log file name for the current log file does not include the date. You can add the date to the current log file; however, the log file will not be rolled over. In addition, the web.temdir variable for setting the log file location is no longer supported; use the pega.logdir variable instead.

For more information, see Pega Platform logging with the Log4j 2 logging service.

Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade

Valid from Pega Version 7.3

If you used node classification in Pega® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type. Agent schedules for standard Pega Platform agents are deleted and re-created with the new node type name, but any customization that you made in Pega 7.2.2 is not saved. You must manually update the agent schedules for standard Pega Platform agents in Pega 7.3.

For more information, see Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3 and the appropriate Deployment Guide.

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