- Release Notes
- 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-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-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
- Trigger-based Attended Automation
- Recording
- UI Elements
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- VMware Horizon Automation
- Salesforce Automation
- SAP Automation
- macOS UI Automation
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- 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
- Chrome Extension on Mac
- 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
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for Safari
- Extension for VMware Horizon
- 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
Linking a Project to an Idea in Automation Hub
linkThe integration between Studio and Automation Hub enables you to easily link Studio projects to ideas in Automation Hub:
- In Studio, you can link any project to an existing idea in Automation Hub by adding the idea URL in the project settings.
- In Automation Hub, for any idea that is in the Development phase and has the Not Started status, you can select to start development in Studio, which automatically opens your Studio instance and creates a new project that is linked to the idea.
As a prerequisite, Studio must be connected through interactive sign-in to an Orchestrator tenant where the Automation Hub service is enabled. You can add Automation Hub URL links from any Automation Cloud tenant in your organization.
Linking a Studio Project to an Existing Idea in Automation Hub
linkTo link a Studio project to an idea in Automation Hub:
- Open the project in Studio.
- Select the Project panel > Project Settings
> General.
- In the Automation Hub URL box, enter the URL of the idea you want the project to be linked to, and then click OK.
If the URL is valid, the project is linked to the idea.
Managing the link to an Automation Hub idea
- To change the idea a project is linked to, repeat the steps in the linking procedure and replace the existing Automation Hub URL with the URL of a different idea.
- To navigate to the idea a project is linked to in Automation Hub, in the Project Settings window, click the
icon next to Automation Hub URL.
Starting a New Project From an Idea in Automation Hub
linkThe option to start a Studio project from an idea in Automation Hub is available to users with the Start Development of projects assigned to CD Power Users permission, which can be assigned to any role in Automation Hub. After the permission is assigned, the user has the Start development in Studio option on ideas that are in the Development phase and have the Not Started status, regardless of their source or Development type. The status of the idea is changed from Development - Not started to Development - In Progress if the Start Development in Studio button is triggered.
To start a new Studio project from Automation Hub:
- Open the Automation Profile of an idea that is in the Development phase and has the Not Started status.
- In the Automation Profile, select More Actions on the lower-left side of the screen, and then select Start Development in Studio from the Actions menu.
- Depending on whether Studio is installed on your machine, proceed as follows:
- If Studio v2021.10 or higher is installed, a browser pop-up prompts you to open Studio. If you accidentally close the browser pop-up, you can still open Studio by clicking the open the app link before moving to the next step
-
If Studio is not installed or a version prior to 2021.10 is detected, download Studio using the options on the page. After you install Studio, click the open the app link to move to the next step.
- A new Studio instance opens with the New Blank Process window for creating a new process. The idea title is added as the process name.
- Configure the process details and click Create.
The process is created and the idea URL is automatically added to the Automation Hub URL field in the project settings.