Work attachment indexing fails with IBM SDK Java 6
Valid from Pega Version 7.1.7
Indexing of work attachments fails when you use IBM SDK Java 6 with Pega 7.1.7 through Pega 7.2. The workaround is to switch to IBM SDK Java 7 or Oracle JDK Java 1.6. You can also disable attachment indexing from the Search landing page; however, if you do this, you are not be able to search the content of attachments.
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.
Child case queries performance can be slow
Valid from Pega Version 7.2
Some customers have reported that performance is slow when they execute queries on child cases. This issue is often indicated by PEGA0005 (query time exceeded limit) alerts that can be correlated to these queries in the logs. To resolve the issue, add a database index to each of your work tables by using a multicolumn index on the pxCoverInsKey, pxObjClass, and pyStatusWork columns.
See Performance improvements for child case queries.
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.
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.
Immediate drain available for the quiesce process when using high availability
Valid from Pega Version 7.2.1
The quiesce process, which is used to take a server out of service for maintenance in a highly available system, can now be modified to use the immediate drain method. When using the default slow drain method for quiesce, users are placed in a passivation queue. When using the immediate drain method, users can continue to access the node being quiesced until it is removed from the load balancer.
Organizations should determine which quiesce method to use based on the overall needs of their users. However, for applications that have implemented long poll requests, it is recommended to use the slow drain method.
For more information, see the Pega 7.2.1 High Availability Administration Guide.
Access work items directly after login
Valid from Pega Version 7.2.1
You can now directly access work items that you receive as email notifications or URLs. The Pega 7 Platform opens the work item after successful user authentication instead of redirecting you to the portal. For a valid user, the type of authentication or number of failed login attempts does not affect this direct access.
For systems that use basic or secure basic authentication, administrators can disable the redirect URL by setting the authentication/basicschemes/redirectToLoginScreen switch to false.
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).
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.
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.