Push real-time notifications to your clients
Valid from Pega Version 7.2.2
You can now set up a real-time notification system based on the publish/subscribe (pub/sub) messaging pattern where a node in the cluster can push notifications to your browser clients. Nodes publish notifications to a channel that can broadcast to all the subscribed browser clients.
You can create a notification channel from the Notification channels landing page and subscribe to the channel by selecting the On Load action, which is available under action sets.
For more information, see Real-time applications and push notifications in the Pega 7 Platform.
PegaDISTRIBUTION Manager (PDM) is no longer available
Valid from Pega Version 7.1.9
The PegaDISTRIBUTION Manager (PDM) is no longer available in the Pega 7 Platform. The related PDN articles and help topics have been archived.
Enhancing the performance of your Next-Best-Action strategy with globally optimized strategies
Valid from Pega Version 8.6
Starting in version 8.6, Pega Platform™ combines the versatility of Next-Best-Action Designer with strategy performance enhancements provided by using globally optimized strategies (GOS). Decrease the run time and memory usage of executing the Next-Best-Action strategy in batch or real-time scenarios by using the globally optimized strategies generated by Next Best Action Designer.
GOS is supported by Pega Platform's standard business change management process. GOS rules are automatically included in relevant revision packages.
For more information, see Enhance the performance of your Next-Best-Action strategy with globally optimized strategies (8.6).
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.
Enhanced security of Robotic Desktop Automation requests
Valid from Pega Version 7.3
Security enhancements have been introduced in the communication (data synchronization or pulling data) between your application that uses robotic desktop automation functionality and Pega® Platform. These applications (web, desktop, and legacy) communicate with Pega Platform through connectors. No additional configuration is necessary.
For more information, see Robotic automation.
The worklist appears to be empty when you go back from an opened case in an offline-enabled mobile application
Valid from Pega Version 7.4
In a Pega® Platform offline-enabled application, when you go back to the worklist from an opened case, the worklist appears to be empty even though it contains cases. This issue will be fixed in the next release of Pega Platform. Only portals that use the key principles and design of the pyCaseWorker portal are supported in offline-enabled applications.
For more information, see Offline mobility guidelines.
Security fields in JFrog Artifactory repository rule form removed
Valid from Pega Version 8.1
The fields in the Security section of the JFrog Artifactory repository rule form, including the Secure protocol field, the Truststore field, and the Keystore field, were not functional in Pega Platform™ 7.3, 7.3.1, and 7.4. This section has been removed from the JFrog Artifactory repository rule form in Pega Platform 8.1.
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.
Unicode-enabled database for international language support
Valid from Pega Version 7.2.1
The Pega 7 Platform database has been enhanced to natively support Unicode multibyte character set encoding when using Postgres on Pega Cloud. This enhancement allows you to store data in languages such as Japanese, Chinese, and Korean.
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.