- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating applications running under a different Windows user
- Automating applications running in AppContainer mode
- Automating applications running as administrator
- Validation of large Windows-legacy projects takes longer than expected
Extension for Chrome
Initially announced for 2023, the end of support for MV2 has been postponed. The timeline of the MV2 phase-out plan will be announced at least 6 months in advance.
The UiPath Extension for Chrome MV2 installed by older versions of
UiPathStudio.msi
will stop working in Chrome. We highly recommend
upgrading your UiPath Studio and Robot installations before this happens.
See the full timeline for the Chrome migration to MV3 extensions here.
The UiPath Extension for Chrome MV3 is available starting with the following UiPathStudio.msi
versions:
- 2022.10
- 2022.4
- 2021.10.8+
- 2020.10.14+
- 2019.10.9+
These versions can be downloaded from:
- Product Downloads in the UiPath Customer Portal
- Resource Center in the UiPath Automation Cloud. To access Resource Center you need to login in your Automation Cloud Organization and click the Help button on the left navigation bar.
This extension helps you create browser automations in Google Chrome.
You can install this extension in multiple ways, as shown below:
Install from UiPath Studio
- Open Studio.
- Navigate to Home > Tools > UiPath Extensions.
-
Select Chrome > Install. Choose one of the available methods from the drop-down:
- Group Policy Offline
- Group Policy Online
- All Users
- Current User
- Native Host Only
- Open Chrome and navigate to
chrome://extensions
. - Enable the UiPath Web Automation extension if needed.
Install from the Studio installer
- Run the
UiPathStudio.msi
installer. - Select an install mode, and then select Advanced Settings > Extensions > UiPath extension for Chrome. If Chrome is installed on your machine, the option is selected by default.
- Click Install. Studio setup continues while also installing the extension for Chrome.
The UiPath Extension for Chrome can also be installed from the command line of UiPathStudio.msi.
Install from Group Policy
You can also install the UiPath Extension for Chrome by using Group Policies. This method silently installs the extension and enables it, without requiring user confirmation.
Offline
The Group Policy Offline installation method requires that the target machine is joined to a Microsoft Active Directory domain or Azure Active Directory.
It does not require access to the Chrome Web Store so it can be used for machines that have restricted Internet access.
UiPathStudio.msi
uses this installation
method by default if its requirements are met.
You can also use this installation method by running from an elevated command prompt:
&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /chrome-policy-offline /silent
&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /chrome-policy-offline /silent
If your organization uses Group Policies for browser extension management then the following changes are also required:
-
In the ExtensionInstallForceList policy, add the value:
ndmegdjihnhfmljjoaiimbipfhodnbgf;file:///C:/ProgramData/UiPath/UiPath.Common/ChromeExtension_SelfHosted/extension_manifest_chrome.xml
-
In the NativeMessagingAllowList policy, add the value:
com.uipath.chromenativemsg_v2
- Set DeveloperToolsAvailability
Group Policy to the value
1
(Allow usage of the Developer Tools) to enable the full extension functionality. For more information, please check the troubleshooting page.
If you need to host the UiPath extension in your internal Web Store you can find the
.crx
file at this location:
C:\Program
Files\UiPath\Studio\UiPath\BrowserExtension\uipath_extension_for_chrome_self_hosted_mv3.crx
Online
The Group Policy Online installation method requires that the target
machine has access to the Chrome Web Store
(https://clients2.google.com/service/update2/crx
and
https://clients2.googleusercontent.com/crx
).
UiPathStudio.msi
uses this installation method if its requirements are met and the machine is not joined to a
Microsoft Active Directory.
You can also use this installation method by running from an elevated command prompt:
&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /chromepolicyglobal /silent
&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /chromepolicyglobal /silent
If your organization uses Group Policies for browser extension management then the following changes are also required:
-
In the ExtensionInstallForceList policy, add the value:
jfcmnbofjlffnejneillkgbniiidiigd;https://clients2.google.com/service/update2/crx
-
In the NativeMessagingAllowList policy, add the value:
com.uipath.chromenativemsg_v2
- Set DeveloperToolsAvailability
Group Policy to the value
1
(Allow usage of the Developer Tools) to enable the full extension functionality. For more information, please check the troubleshooting page.
Uninstalling
The UiPath Extension for Chrome can be uninstalled by running from an elevated command prompt:
&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /chromecleanup /silent
&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /chromecleanup /silent
You can also uninstall by opening Studio, navigating to Home > Tools > UiPath Extensions, and selecting Chrome > Uninstall. The extension will be uninstalled with the same method used for the installation. This method is displayed in the disabled drop-down next to the Uninstall button.
Chrome version requirements
The UiPath Extension for Chrome MV2 requires Chrome version 64 or greater.
The UiPath Extension for Chrome MV3 requires Chrome version 98 or greater.
When using one of the installation methods described above, the browser version will be checked and the extension with the appropriate format (MV2 or MV3) will be automatically installed.
New extension features
Automating Chrome apps
Starting with UiPathStudio.msi
2022.4 the UiPath Extension for Chrome can be used to automate Chrome Apps.
Troubleshooting
Your system administrator might have configured Group Policies that prevent the UiPath Extension for Chrome from working. To enable it, please follow the instructions from the Group Policies page.
For any other issues regarding the UiPath Extension for Chrome, please view the detailed troubleshooting page.