Pega File Listener process changes
Valid from Pega Version 7.2.2
Beginning with Pega 7.2.2, File Listener processes files in a different way:
- File movement in directories – Previously, files were processed from the Work directory. In Pega 7.2.2, files are processed from the source location. Files move to the Work directory only if the initial processing fails and Recovery is disabled.
- New file processing – Previously, File Listener would process all files in the source location, even if the files were added during the processing. In Pega 7.2.2, files added to the source location during processing are read the next time the File Listener starts.
For more information, see File Listener data instances.
Functionality of the pyInvokeRESTConnector rule and the pxDeferenceEndpoint rule moved to core engine
Valid from Pega Version 7.2.2
The functionality of the pyInvokeRESTConnector rule and the pxDeferenceEndpoint rule has been moved into the core engine code of the Pega 7 Platform. This change provides more consistent behavior, reduces maintenance, and reduces the risk of regression issues. As a result, you can no longer customize these rules, and upgrading the Pega 7 Platform requires special considerations if you previously customized these rules.
For more information, see Upgrading with customized pyInvokeRESTConnector and pxDeferenceEndpoint rules.
Send and receive queued messages securely with IBM MQ servers
Valid from Pega Version 7.2.2
You can now configure applications developed on the Pega 7 Platform for secure message queuing with IBM MQ servers by using the MQ server rule form. You secure the connection by specifying the cipher suites with encryption standards that meet your requirements and the SSL/TLS X.509 certificates that you use for authentication.
For more information, see Configure secure message queuing with IBM MQ servers.
Single sign-on (SSO) support for Box
Valid from Pega Version 7.2.2
You can now use SSO integration with Box so that users who have already been authenticated are not asked to reauthenticate when accessing Box from their Pega application. The Pega application and the Box application must use the same identity provider federation. This capability provides an integrated user experience and supports automated case processing of attachments.
For more information, see Authentication Profile data instances - Completing the OAuth 2.0 tab.