Upcoming feature deprecations
- Updated: 2024/08/13
Upcoming feature deprecations
Review the features and capabilities (from Automation Anywhere or third party) that are nearing deprecation to understand how they affect your automation and what action is required.
You can use the specified alternatives or updated versions when they are made available.
Upcoming third-party deprecations
The following table lists third-party features that will be deprecated by the date mentioned:
Feature or capability | Deprecation date | Customer impact and recommendation | Resources |
---|---|---|---|
Oracle Database support | With v.34 release (planned for September 2024) | Starting from Automation 360 v.34 release, support for installing Control Room on the Oracle Database will not be available. Microsoft SQL Server will be the only database type that will be available for installing Control Room. | Guidance to be provided in September |
Microsoft Azure ACS deprecation | April 2, 2026 |
Microsoft is retiring Azure ACS and recommends migrating to their modern authentication platform, Microsoft Entra (formerly Azure AD). Recommended:The Automation 360 SharePoint package is fully compatible with Entra. Simply set up your OAuth clients and use them within the SharePoint package to ensure a smooth transition and avoid any disruption to your SharePoint automations. |
|
Google Less Secure Apps (LSAs) deprecation |
September 30, 2024 |
Google has announced the deprecation of Less Secure Apps (LSAs) to connect to Google Workspace using a username and password as this authentication is not secure and does not meet the industry's best practices. Google recommends using a more secure OAuth2-based authentication to connect to Gmail. If you are using Automation 360 to automate Gmail using Email and Email Trigger packages with Basic authentication, then you will be impacted by this deprecation. The latest Automation 360 version of the Email package provides you an option to switch from Basic authentication to OAuth2 - PKCE. However, the same option is not available in the Email Trigger package. To help reduce the risk of deprecation, we plan to enhance the Email and Email trigger packages with a new Control Room managed OAuth2 mode of authentication that you can use to automate Gmail. This authentication mode is secure and uses the centralized access token management from the Control Room. A similar solution has already been provided for Google packages. For details, see Connect action for Google packages Recommended: We plan to provide a Bot Scanner utility to help you scan and identify the impacted bots that use the Email and Email trigger packages to automate Gmail. You can then update the impacted bots by replacing the Basic authentication with Control Room managed OAuth2 authentication mode. |
Upcoming Automation Anywhere deprecations
The following table lists Automation Anywhere features that will be deprecated by the date mentioned:
Feature or capability | Deprecation date | Customer impact and recommendation | Resources |
---|---|---|---|
Connect Learning Instances from IQ Bot feature in Document Automation | January 2025 | This deprecation will impact customers who are using the Connect Learning Instances from IQ Bot feature in Document Automation. We recommend that such customers use the IQ Bot - Document Automation Bridge package to use the IQ Bot learning instances in Document Automation. See IQ Bot - DA Bridge package. | For assistance, contact Automation Anywhere support: Open a support case (A-People login required). |
Cloud Migration Utility | September 30, 2024 | This deprecation will impact customers who are using Enterprise 11 and are planning to use the Cloud Migration Utility to migrate to Automation 360 Cloud. The Cloud Migration Utility will be supported for releases we plan to deliver up to September 2024 (planned Automation 360 v.33 release). We recommend that such customers use the utility to migrate to the latest available Automation 360 Cloud GA release before September 30, 2024. | For assistance, contact Automation Anywhere support: Open a support case (A-People login required). |
Enterprise 11 Control Room to Automation 360 On-Premises upgrade tool | With v.34 release (planned for September 2024) | This deprecation will impact customers who are planning to upgrade from Enterprise 11 Control Room to Automation 360 On-Premises deployment, which currently uses the installer package's upgrade option. This upgrade tool is scheduled for deprecation from Automation 360 v.34 release. We recommend customers to complete the upgrade to Automation 360 before September 30, 2024. | Prepare to manually migrate to Automation 360 Cloud |
EST, HST and MST time zones | - | The EST, HST or MST time zones will no longer be supported while scheduling a Task Bot, API Task, or a process. | Schedule a bot | How to schedule API Tasks |
Upcoming Automation Anywhere API deprecations and EoLs
The following table lists Automation Anywhere Control Room APIs that will be deprecated and discontinued by the dates mentioned:
- API deprecation indicates that an API is no longer recommended for use but is functional. Developers are encouraged to migrate to newer, supported versions of the API. The API will be available till the End of Life (EoL) date to enable a smooth transition.
- API EoL (End of Life) indicates the date when the API will cease to function, and will no longer be available for use. Developers should have completed their migration to the newer, supported versions of the API before this date.
Feature or capability | Deprecation date | EoL date | Customer impact and recommendation | Resources |
---|---|---|---|---|
v1 Bot Scheduler APIs | With v.34 release (planned for September 2024) | With v.37 release (planned for June 2025) | The v1 Bot Scheduler APIs
(/v1/schedule/automations ) will be
deprecated. Recommended: Use the v2 Bot Scheduler APIs
|
|
v3 Work Load Management (WLM) APIs | With v.34 release (planned for September 2024) | With v.37 release (planned for June 2025) | The following v3 Work Load Management (WLM) APIs are getting
deprecated:
Recommended: Use the v4 WLM APIs that will be available
with the v.34 release:
|
Completed deprecations: For a list of features already deprecated, see Completed feature deprecations.