A manifest is a specification that is essential for constructing browser extensions, detailing the necessary components and permissions required for the extension functionality. Manifest V3 (MV3) is the latest specification for browser extensions supported by Chromium-based browsers, including Microsoft Edge.

Deprecation of Manifest V2 (MV2) extension

Microsoft has adopted the same MV3 migration path in Microsoft Edge browser as Google Chrome. As Google is deprecating MV2 based extension, ensure that you update to Manifest V3 (MV3) based extensions for enhanced security, privacy, and performance. Continuing to use MV2 extension might impact your existing automations that use this extension for Google Chrome and Microsoft Edge browsers.

For Google Chrome MV2 extensions timelines, see Manifest V2 support timeline.
For Microsoft Edge MV2 extensions timelines, see Overview and timelines for migrating to Manifest V3.

Note: Manifest V2 extensions are no longer available in the Google Chrome web store. However, if you have the direct URL to a Manifest V2 extension, you can still access it.

Automation 360 deprecation of Manifest V2 (MV2)

In Automation 360 v.25 release, we introduced the Manifest V3 (MV3) extensions for Google Chrome and Microsoft Edge browsers. For more information, see Automation 360 v.25 Release Notes.

For information on Automation 360 deprecation of MV2 extension, see Completed feature deprecations.

Automation 360 features that use browser extensions

The following Automation 360 features use browser extensions for web applications running on Google Chrome or Microsoft Edge:

Bot Agent device registration with the Control Room (uses Chrome extension only)
Automation of web applications through Universal Recorder or Browser package
User interface based triggers
Packages that use window titles, for example, OCR and Mouse Click

Choose your Manifest V3 extension update path

Note: Manifest V3 extension is supported on Google Chrome and Microsoft Edge browsers version 91 and later only.

Updating to Manifest V3 extension

New customers: Users starting with Automation 360 v.26 will directly use Manifest V3 extensions. You will not be impacted by the deprecation of Manifest V2 extensions.
Cloud customers: Our Cloud deployments is updated to Automation 360 v.26 in October, and customers can switch to Manifest V3 extensions when they update their Bot Agent.
On-Premises customers:
- Automation 360 v.26: Customers updating from an earlier version to Automation 360 v.26 will switch to Manifest V3 extensions when they update their Bot Agent.
- Automation 360 v.25: We have provided a Control Room patch with Automation 360 v.25. After installing the patch, the V2 extensions is switched to Manifest V3 extensions when you update the Bot Agent.
- Automation 360 (v.24, v.23, and v.22): For customers on Automation 360 v.24 or earlier, we strongly recommend that you update to Automation 360 v.26 or later releases. .
- Automation 360 v.21 or earlier: We strongly recommend that you update to the latest version of Automation 360.

Migrating to Automation 360

We recommend that you migrate to Automation 360 v.26, which uses Manifest V3 extensions by default. If you are migrating to Automation 360 v.25, install the Control Room patch, that we released in October. See Automation 360 v.25 Release Notes.

Enterprise 11 customers

For details, see Enterprise 11: Deprecation of Basic authentication and MV2 extensions.

Automation 360

Google Chrome and Microsoft Edge Manifest V3 extensions