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.
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.
Child case queries can be slow after upgrade
Valid from Pega Version 7.2.1
After upgrading, performance might be slow when you run queries on child cases for work tables that existed prior to the upgrade. 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.
For more information, see Performance improvements for child case queries.
The UpdateAdaptiveModels agent causes an exception after Pega 7.2 to 7.2.1 upgrade
Valid from Pega Version 7.2.1
After the Pega 7 Platform is upgraded from version 7.2 to 7.2.1, the log files might show an error that is caused by the UpdateAdaptiveModels agent. This agent is enabled by default and is responsible for updating scoring models in the Pega 7 Platform. If you use adaptive models in your solution, you can avoid this error by configuring the Adaptive Decision Manager service. If you do not use adaptive models, disable the UpdateAdaptiveModels agent.
For more information, see Configuring the Adaptive Decision Manager service and Pega-DecisionEngine agents.
Reconfiguration of the Adaptive Decision Manager service after upgrade to Pega 7.2.1
Valid from Pega Version 7.2.1
After you upgrade the Pega 7 Platform to version 7.2.1, you need to reconfigure the Adaptive Decision Manager service. Beginning with Pega 7.2.1, the Adaptive Decision Management (ADM) service is native to the Pega 7 Platform and is supported by the Decision data node infrastructure.
For more information, see Services landing page.
Customizations to the prlogging.xml file must be manually ported after upgrade
Valid from Pega Version 7.3
As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, the name of the logging configuration file has changed from prlogging.xml to prlog4j2.xml and the format of the file has changed considerably. If you customized your prlogging.xml file, port the customizations to the new prlog4j2.xml file. If you do not port the changes, the Pega® Platform uses the default prlog4j2.xml file and disregards your customized prlogging.xml file.
For more information about customizing your log files, see the Apache Log4j 2 documentation.
Socket server has changed for remote logging
Valid from Pega Version 7.3
As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, the socket server that is used for remote logging has changed from the Log4j remote logging package with the LogFactor5 log analysis tool to TcpSocketServer. If you use remote logging, update your socket server to TcpSocketServer. For more information, see Installing and using remote logging.
New process for Pega Cloud customers to obtain BIX extract files
Valid from Pega Version 7.3
The process for obtaining Business Intelligence Exchange (BIX) extract and manifest files for Pega® Cloud customers has changed as a result of data security enhancements for HIPAA compliance. By default, after upgrading to Pega 7.3, you must obtain the BIX extract and manifest files from the Pega SFTP server. From within Designer Studio, you can configure the BIX extract and manifest files to be sent to a remote SFTP server by a file listener. For Pega Cloud customers who have purchased a Pega Cloud SFTP Server subscription, you can configure BIX to send the BIX extract and manifest files to the SFTP server's folders for remote SFTP client download.
For more information about obtaining files from the Pega SFTP server, see Obtaining BIX extract files from the Pega SFTP server.
For more information about having files sent to your SFTP server, see Defining SFTP-related data instances.
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.
Requestor Management landing page access privileges
Valid from Pega Version 7.3
To access the Requestor Management landing page after upgrading to Pega® Platform 7.3, you need to add the appropriate privileges to the @baseclass and Pega-Landing access classes in the access roles. Apply these privileges to any application in which you want the operator to be able use the requestor management feature.
For more information, see the Requestor Management landing page and the appropriate Deployment Guide.