Chrome and Edge Manifest V3 extensions

As Google will deprecate Manifest V2 extensions by June 2023, this might impact your existing automations that use our current Manifest V2 extensions for Chrome and Edge browsers. We plan to publish Manifest V3 extensions with the next release Automation 360 v.26 to help you start switching to Manifest V3 extensions.Manifest V3 transition timeline

Manifest V2 deprecation

A manifest is a specification using which browser extensions are built. As Google is deprecating Manifest V2 extensions, we recommend you plan to switch to Manifest V3 extensions, which provide enhanced security, privacy, and performance.

Impact to our customers: Automations that use our current Chrome and Edge Manifest V2 extensions will stop working by June 2023. You can choose to use the enterprise group policy to continue to use Manifest V2 extensions till Jan 2024. However, post this date, you have to switch to V3 extensions for your automations to work. Manifest V3 transition timeline

For more information on Manifest V2 and support timelines, see these pages:

Automation 360 features that use browser extensions

The following Automation 360 features use the Chrome or Edge browser extension for web applications running in Chrome or 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

Plan the switch to Manifest V3 extensions

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

Automation 360 customers:

We plan to publish new Chrome and Edge Manifest V3 extensions with the Automation 360 v.26 release. We will also continue to support Manifest V2 extensions until June 2023 to provide you time to switch to Manifest V3 extensions before Jan 2024 Manifest V3 transition timeline. You have the following options to switch to Manifest V3 extensions:

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 will be updated to Automation 360 v.26 by mid-October, and customers will switch to Manifest V3 extensions when they update their Bot Agent.
On-Premises customers:
- Updating to 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.
- v.25: We will provide a Control Room patch for Automation 360 v.25 by October. After installing the patch, customers will switch to Manifest V3 extensions when they update their Bot Agent.
- 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. If you choose not to update, we will provide a set of steps to perform on all Bot Agent and Bot Runner devices to switch to Manifest V3 extensions.
- v.21 and earlier: We strongly recommend that you update to the latest version of Automation 360.
  注： You can choose to delay switching to MV3 extensions by using a Chrome group policy that extends support for Manifest V2 extensions until Jan 2024. Manifest V3 transition timeline.

Customers 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, you will have to install a Control Room patch, which we plan to release by October.

Extend Manifest V2 extensions usage through group policy

You can choose to use the enterprise group policy to continue to use Manifest V2 extensions till Jan 2024. Manifest V3 transition timeline

You can extend the Manifest V2 deprecation only using the group policy. This extension provides you adequate time to plan upgrading to Manifest V3 extensions. You can use any extension group policy to extend the use of Manifest V2 extensions.

To update the policy, perform these steps:

Copy the following entries to a .txt file and save the file as a .reg file.

Chrome:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist]
"ExtensionSettings"="{\"bboccnojhhoegfffpcllbeigipedjedf\":{\"installation_mode\": \"normal_installed\",\"update_url\": \"http://clients2.google.com/service/update2/crx\"}}"

Edge:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist]
"ExtensionSettings"="{\"fnmjcdajlonpigpcfnemeikipmolbfii\":{\"installation_mode\": \"normal_installed\",\"update_url\": \"https://edge.microsoft.com/extensionwebstorebase/v1/crx\"}}"

Run the .reg file.
Restart the browser for the changes to take effect.