- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Logging
- The Diagnostic Tool
- Workflow Analyzer
- 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-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-021 - Hardcoded Timeout
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- 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-017 - Invalid parameter modifier
- 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
- Variables
- Arguments
- Imported Namespaces
- Coded automations
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Troubleshooting
- Trigger-based Attended Automation
- Object Repository
- The ScreenScrapeJavaSupport Tool
- Extensions
- About extensions
- SetupExtensions tool
- Hardware and software requirements
- Task Scheduler
- Side-by-side support
- Adding Remote Runtime dependencies
- New extension features
- Chrome extension is removed automatically
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Edge version requirements
- Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- List of extensions for Edge
- Extension for Citrix
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Studio testing
- Troubleshooting
- About troubleshooting
- Assembly compilation errors
- 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
- Validation of large Windows-legacy projects takes longer than expected
Studio User Guide
If your organization uses Group Policies for browser extension management then follow the instructions from this page to ensure that the extension for Edge is installed correctly.
edge://policy.
You can find out more information about Edge policy management on this page.
ExtensionInstallForcelist
The ExtensionInstallForcelist policy controls which extensions are force-installed in the browser.
-
For machines that are joined to a Windows Active Directory follow the installation steps for the Group Policy Offline installation method.
For this installation method the ExtensionInstallForcelist policy must contain the value:
ndmegdjihnhfmljjoaiimbipfhodnbgf;file:///C:/ProgramData/UiPath/UiPath.Common/EdgeExtension_SelfHosted/extension_manifest_edge.xml -
For machines that are not joined to a Windows Active Directory follow the installation steps for the Group Policy Online installation method.
For this installation method the ExtensionInstallForcelist policy must contain the value:
cdfjcmjmgdnojgaojdnefhjjpaijapci;https://edge.microsoft.com/extensionwebstorebase/v1/crx
NativeMessagingBlocklist
ChromeNativeMessaging.exe) from working.
NativeMessagingBlockList policy is defined with the value of
*, it means all native messaging hosts are denied, unless they
are explicitly allowed through the NativeMessagingAllowList
policy.
NativeMessagingAllowlist
The NativeMessagingAllowlist policy specifies which native messaging hosts are not subject to the deny list.
* means all native messaging hosts are
denied. You can allow the UiPath NativeHost by adding the value
com.uipath.chromenativemsg_v2 to the
NativeMessagingAllowlist policy.
ExtensionInstallBlocklist
The ExtensionInstallBlocklist policy prevents extensions from being installed on the machine.
To fix this, you can either:
- Install the UiPath Extension using Group Policy.
- Or allow the UiPath Extension to
be installed from the Edge Web Store by adding the value
cdfjcmjmgdnojgaojdnefhjjpaijapcito the ExtensionInstallAllowlist policy.
NativeMessagingUserLevelHosts
false, it prevents the UiPath extension from working correctly
in the case it was installed without administrator privileges.
To fix this, you can either:
- Install the UiPath Extension using Group Policy.
- Set the
NativeMessagingUserLevelHosts policy to
true.
BlockExternalExtensions
true, it prevents the UiPath extension from being installed in
any other way except for by policy.
To fix this you can either:
- Install the UiPath Extension using Group Policy.
- Set the
BlockExternalExtensions policy to
false.
ExtensionAllowedTypes
extension to the ExtensionAllowedTypes
policy.
ExtensionSettings
If the ExtensionSettings policy is set to block all extensions it will prevent the UiPath Extension from being installed.
To fix this you can either:
- Install the UiPath Extension using Group Policy.
- Or allow the UiPath Extension to
be installed from the Edge Web Store by adding the value
cdfjcmjmgdnojgaojdnefhjjpaijapcito the ExtensionInstallAllowlist policy.
