Version 11.3.4.8 Release Notes

The Version 11.3.4.8 release includes Enterprise Client support for OAuth2 authentication for IMAP and POP3 protocols for email automation.

This release includes only the Enterprise Client patch installer. You have to install only the Enterprise Client for this patch.

Microsoft will permanently disable Basic authentication for specific protocols in Exchange Online starting from October 1, 2022. This impacts customers running bots for email automation and email trigger that connect to Exchange Online using IMAP or POP3 protocols with Basic authentication. We recommend that you start using OAuth 2.0 for email automation and email trigger.

Feature in this release

Enterprise Client
Use OAuth2 authentication for IMAP and POP3 protocols
We now provide OAuth2 authentication support for IMAP and POP3 protocols used in the Email Automation and Email trigger. You can use OAuth2 – Client credentials and OAuth2 – Authorization code with PKCE to authenticate with the mail server for email automation.
Note:
  • OAuth 2 is not supported for EWS server. When you upgrade to Version 11.3.4.8, the existing bots created using the EWS server will not work. We recommend you connect to IMAP/POP3 protocols using OAuth 2.0 to run your bots successfully.
  • Email trigger support only OAuth2 – Client credentials whereas the Email Automation command supports both OAuth2 – Client credentials and OAuth2 – Authorization code with PKCE.

Fixed features

Enterprise Client
When you upgrade from Version 11.3.4.2 to Version 11.3.4.7 and launch Automation Anywhere client, you can now create or edit MetaBot in the MetaBot Designer designer window. Previously, the MetaBot Designer window was not opening.

Service Cloud case ID: 01828637