- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- 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-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
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Control Flow
- Object Repository
- Logging
- The ScreenScrapeJavaSupport Tool
- Studio testing
- Extensions
- Troubleshooting
- 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
- 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.
This policy must contain the ID of the UiPath Extension for Edge.
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:
dknkgjgkdpkmddgdjlgdhfojlaehikmk;https://edge.microsoft.com/extensionwebstorebase/v1/crx
DeveloperToolsAvailability
1 (Allow usage of the Developer Tools) to enable
the full extension functionality.
See more details about this setting in the troubleshooting page.
NativeMessagingBlocklist
ChromeNativeMessaging.exe) from
working.
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
dknkgjgkdpkmddgdjlgdhfojlaehikmkto 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
dknkgjgkdpkmddgdjlgdhfojlaehikmkto the ExtensionInstallAllowlist policy.
