Completed feature deprecations
- Updated: 2024/08/21
Completed feature deprecations
Review the features and capabilities (from Automation Anywhere or third party) that are already deprecated and review how they affect your automation.
For a list of features nearing deprecation, see Upcoming feature deprecations.
Third-party deprecations
The following table lists third-party features that are already deprecated:
| Feature or capability | Deprecation date | Customer impact and recommendation | Resources |
|---|---|---|---|
| Manifest V2 based extensions (Automation 360 v.26 and later releases) | October 23, 2023 | From Automation 360 v.26 and later releases, we
have published new Google Chrome and Microsoft Edge Manifest V3 extensions.
Starting on October 23, 2023, we will deprecate support for Manifest V2 extensions on Automation 360 v.26 and later releases. After this date, we will not address any issues relating to Manifest v2 extensions. If you are on Automation 360 v.26 or a later release and still using Manifest V2 extensions for Google Chrome and Microsoft Edge, we recommend that you update your Google Chrome and Microsoft Edge browser extensions to Manifest V3 extensions before October 23, 2023. |
|
| Tegaki API OCR engine | October 3, 2023 | From Automation 360v.30, we have deprecated use of Tegaki API OCR engine for data extraction in Automation 360 IQ Bot. We recommend using the Google Vision OCR engine instead. |
Deprecation note added to:
|
| Transport Layer Security (TLS) 1.0 and TLS 1.1 | April 2023 | Automation 360
Cloud deployments currently support the
following TLS protocol versions:
Note: For Automation 360
Cloud deployments, the changes will be
effective as part of the Cloud
deployment configurations, not as part of the Automation 360 release.
|
Deprecating TLS 1.0 and TLS 1.1 |
|
Manifest V2 based extensions by Google See also: Overview and timelines for migrating to Manifest V3 |
January 2023 |
Automations that use Google Chrome Manifest V2 based
extensions will stop working sometime after June 2023. The
deprecation timelines of Manifest V2 based extensions are
currently under review and subject to change by Google.
Recommended: Switch to Manifest V3 based extensions for Google Chrome and Microsoft Edge. Releases:
|
|
|
EWS API See Upcoming API Deprecations in Exchange Web Services for Exchange Online |
March 31, 2022 | Automation 360 currently uses EWS API in Email
package and Email trigger for the EWS option to
connect to Exchange Online hosted on Azure Cloud and access
emails from Microsoft 365. Microsoft has recommended that customers move to a REST-based Graph API, which is more secure and scalable compared with the legacy SOAP-based EWS API. Therefore Automation 360 will provide support for Microsoft 365 Outlook package based on Graph APIs which will enable you to switch from EWS API to Graph API from an upcoming release. This deprecation by Microsoft might impact bots for email automations (Email package and Email trigger) that connect to Exchange Online using EWS API. Note that there is no immediate impact on your existing bots and they continue to run properly. Recommended: Update the impacted bots by replacing each email-related action with the equivalent new actions in the Microsoft 365 Outlook package, planned in the upcoming release if your bots are impacted by the deprecation. |
|
| October 2022 |
Bots for email automations (Email package and trigger) that connect to Exchange Online by using IMAP, POP3, or EWS protocols with Basic authentication will be impacted. Recommended: Update the impacted bots by replacing each email-related action with OAuth 2.0. Released:
|
||
| Internet Explorer EOL | June 2022 |
Customers who are running IE-based bots on Windows 10 Semi-Annual Channel are impacted. Releases with tools to convert IE-based bots
to Microsoft Edge with IE mode:
|
Automation Anywhere deprecations
The following table lists Automation Anywhere features that are already deprecated:
| Feature or capability | Deprecation date | Customer impact and recommendation | Resources |
|---|---|---|---|
| Cloud-enabled deployment model | April 2024 | This deprecation will impact customers who are on a Cloud-enabled deployment model. We recommend that such customers move to Automation 360 Cloud or On-Premises before the deprecation. | For assistance, contact Automation Anywhere support: Open a support case (A-People login required). |
| Reactivation Threshold | March 2024 | This deprecation will benefit customers as it removes the threshold or limit on the number of work items to be queued before the automations are executed. For more information, see Create queues | For assistance, contact Automation Anywhere support: Open a support case (A-People login required). |
| Automation 360 IQ Bot Community Edition | November 28, 2023 |
Automation 360 IQ Bot Community Edition will no longer be available from November 28, 2023. Use the Document Automation Community Edition for enhanced intelligent document processing. Users who have created automations using Automation 360 IQ Bot will need to rewrite them using Document Automation. |
To learn more, refer to Document Automation. |
|
Descoped language support |
June/July 2023 |
Beginning with Automation 360 v.29, the User Interface for Automation Anywhere product will no longer support Italian, Russian, and Simplified Chinese languages. In addition, updated release documentation will no longer be available in these three languages though older documentation will be accessible. |
-- |
| IQ Bot Extraction package | This package is deprecated from Automation 360 v.26. Document Automation provides all the capabilities provided by the IQ Bot Extraction package. To move your bots from the IQ Bot Extraction package to Document Automation, see Move from IQ Bot Extraction package to Document Automation. | Archived Documentation (PDF): | |
| Set session variable action | Year 2022 | This action is deprecated and is no longer available for new bots. Existing bots using this action will not be impacted and will continue to run. You can use a global session to specify a session name for use across multiple bots. |
To learn more, refer to Sharing sessions across bots |
|
IQ Bot Extraction package |
October 2022 |
From Automation 360 v.25, the IQ Bot Extraction package no longer supports pre-trained machine learning model for invoice data extraction but will continue to support learning instance group based-training extraction. Recommended: Use the new command package called Document Extraction, released in v.25 as part of Document Automation. Released: Automation 360 v.25 |
Move from IQ Bot Extraction package to Document Automation |
|
IQ Bot - Tesseract OCR v3 |
October 2022 | For all existing learning instances trained using Tesseract OCR v3, we recommend that you plan to train them
with alternative OCRs (including Tesseract4 OCR)
before you update to v.26. Note that Automation 360 IQ Bot
Cloud customers will receive the v.26
release by default from October 2022. Released: Automation 360 v.26 |
-- |
| G-Suite Apps | September 2022 | From Automation 360 v.26, the GSuite Apps package no longer supports using the
Connect and
Disconnect
actions to establish a connection with the Google
server and automate tasks. Recommended:For specific
G-Suite applications, the functionality of the G-Suite Apps
package is available in the following
G-Suite packages:
|
Connect action for Google packages |
| Automation Anywhere Mobile app | July 2022 | The Automation Anywhere Mobile app is deprecated and will not be updated to subsequent versions of iOS and Android. The mobile app is no longer available and no further support will be offered. A replacement product is currently not available. | Archived Documentation (PDF): EN-US |
| Automation Anywhere for Excel | January 2022 |
Automation Anywhere for Excel has been deprecated. The plug-in is no longer available to download as a product. However, support will be offered to current customers already using the product. A replacement product as a plug-in for Microsoft Excel is not available. However, as an alternative, new customers can develop bots for Excel within the Automation 360 Automation Workspace and use input variables to allow specifying file names, worksheets, and ranges for bots to operate on. In Automation Anywhere for Excel, this action was triggered from within the Excel application, whereas now, this action is taken from the Automation Anywhere Control Room. |
Documentation: Archived docs for RPA Bots for Excel v2.0 |
| IQ Bot [Local Device] package | September 2021 | This package is deprecated from Automation 360 v.22 (Build 10526). We recommend using Document Automation with the Document Extraction package that provides all the capabilities provided by the IQ Bot [Local Device] package along with some improvements. | Archived Documentation (PDF): IQ Bot [Local Device] package (Archived PDF) |
| Process package | January 2021 | The Process package is no longer supported with the Create a
Request action as this has been replaced by the AARI web package
(now renamed to Process Composer package) in
Enterprise A2019.18. Recommended: Use the Create a Request action in Process Composer package. |
New: Process Composer package
Deprecated: Process package |
| Human-Bot Collaboration 11.3.x | August 2020 | Human-Bot Collaboration (HBC) 11.3.x was deprecated from August
2020 with the release of Enterprise A2019.15.
Recommended: Migrate to Automation 360 to use the Automation Co-Pilot for Business Users (Automation Co-Pilot) that includes Desktop and Web.
Note: For this migration, there is no
automated migration path between HBC 11.3.x and Automation Co-Pilot because of an absence of
parity between the two products (including sets of
features).
|
New: Automation Co-Pilot for Business Users
Deprecated: Enterprise 11: Human-Bot Collaboration |
Automation Anywhere API deprecations and EoLs
The following table lists Automation Anywhere Control Room APIs that are already 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 Authentication API | November 2023 | With v.33 release (June 2024) | From Automation 360 v.33, the Authentication
APIs: POST
v1/authenticationand POST
v1/authentication/token are discontinued and
will stop working. Recommended:Use the v2 versions of
the Authentication APIs: POST
|
|
| v1 User Management API | November 2023 | With v.33 release (June 2024) | From Automation 360 v.33, the User Management
APIs: v1/usermanagement are discontinued and
will stop working. Recommended:Use the v2 versions of
the User Management APIs
|
|
| v3 Migration API | November 2023 | With v.34 release (planned for September 2024) |
From Automation 360 v.31, the v3 Migration APIs
( Recommended: Use the v4 version of the Migration API
|
|
| v2 Activity List API | June 2022 | With v.27 release (January 2023) | From Automation 360 v.25, the Activity List API
(v2/activity/list) is deprecated.
Recommended: Use the v3 version of the
Activity List API Note: If you want
to get the
botOutVariables or
callbackInfo, use
/v3/activity/execution/{id}
Bot Execution Orchestrator API V3
. |
Bot Execution Orchestrator API V3 |
See also: Automation 360 software lifecycle policy .