Improved Pega 7 Platform upgrade and update time
Valid from Pega Version 7.2.1
The Pega 7 Platform upgrade and update tools have been improved to streamline indexing. Upgrading and updating are faster than with previous releases.
Ability to import data into a Pega Cloud database
Valid from Pega Version 7.2.1
You can export a custom Pega 7 Platform database table into a CSV file and import it into a Pega Cloud database or other Pega 7 Platform database by using the Data Upload utility. This utility is available only for Postgres databases and tables that do not contain BLOB columns. This utility is useful, for example, for updating a product catalog that is used in a Pega Cloud application.
For more information, see Importing data into a Pega Cloud database.
End of support for Microsoft Internet Explorer 9 in Pega 7.2.1
Valid from Pega Version 7.2.1
In accordance with Microsoft’s announcement to discontinue support for Internet Explorer 9, Pega 7.2.1 will not support Internet Explorer 9. You should not upgrade to Pega 7.2.1 if you are still using Internet Explorer 9. Otherwise, upgrade to Microsoft Internet Explorer 10 or later, or use Google Chrome, Apple Safari, or Mozilla Firefox, which support certain HTML5 and CSS3 standards not supported in Internet Explorer 9.
For more information about browser support, see the Platform Support Guide or contact Pegasystems Global Customer Support.
Ability to schedule schema updates for Pega Cloud
Valid from Pega Version 7.2.1
You can schedule BLOB size and table statistic updates to database schemas to run automatically by using agents. Scheduling schema updates is useful for performance monitoring and tuning in the Pega Cloud. This feature is available only for customers who use a Postgres database.
There is an agent for updating the average and maximum BLOB sizes, and an agent for updating table statistics. Each agent can be configured separately for each schema. You can configure whether to schedule the agent to run daily or weekly. You can deactivate a running schedule on the Schema Tools landing page by clicking . From the Schema Tools landing page, you can configure more complex scheduling on the Edit Agent Schedule landing page. In addition, you can configure these agents by using Dynamic Data System Settings.
For more information, see Scheduling schema updates.
Option to resume failed upgrades and updates
Valid from Pega Version 7.2.1
When you upgrade or update to Pega 7.2.1, you can opt to have the system resume the deployment after a failure to avoid restarting the deployment and to save time. The deployment resumes at the point of failure and does not repeat any successful steps. This functionality is not supported for new installations. For more details, see the Pega 7 Platform Upgrade Guide and the Pega 7 Platform Update Guide.
View and apply schema changes when upgrading or updating
Valid from Pega Version 7.2.1
When you upgrade or update, you can view the schema changes to the default work and history tables and apply the changes to your cloned tables. By applying the changes, you improve performance and can take advantage of the latest reports on those tables.
For information about viewing and applying schema changes as part of the upgrade or update, see the Pega 7 Platform Upgrade Guide or the Pega 7 Platform Update Guide.
For information about using the Designer Studio tool or the command-line tool, see Updating cloned tables after an upgrade or update.
Discontinued support for multithreaded requestors
Valid from Pega Version 7.2.1
Multithreaded requestors are no longer supported in the Pega 7 Platform. Multithreading was previously specified by the prconfig setting initialization/allowMultiplePRThreads. If this setting is set to true when you upgrade to Pega 7.2.1, errors occur during the quiesce process.
Upgrade/update fails if PostGIS is applied to PegaRULES or PegaDATA schema
Valid from Pega Version 7.2.1
If you use the PostGIS extension to a PostgreSQL database, upgrading or updating the Pega 7 Platform fails if the extension has been applied to either the PegaRULES or PegaDATA schema. PostGIS can be applied to any other schema.
Support for Hotfix Manager in service-enabled system management
Valid from Pega Version 7.2.1
You can manage hotfixes by using a REST service from Hotfix Manager in the service-enabled system management utility. With service-enabled system management, you can manage hotfixes simultaneously on more than one Pega 7 Platform system. You can manage the following hotfix operations: install, scan, commit, rollback, and GenerateDDL.
For more information, see Managing hotfixes (service-enabled).
New passivation and activation activities
Valid from Pega Version 7.2.1
Two new activities have been implemented, pyPrePassivation and pyPostActivation, which are run every time operator passivation occurs, regardless of the node quiesce state. These activities save and restore the requestor state during passivation and activation. In order for the pyPrePassivation or pyPostActivation activity to be run as expected, you must implement the activity by using the correct Applies To class (@baseclass).
The previous activities that were run during the quiesce process, pyPreQuiescePassivation and pyPostQuiesceActivation, have been deprecated.
For more information, see the Pega 7.2.1 High Availability Administration Guide.