- 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
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- 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
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User
Linking a Project to an Idea in Automation Hub
The integration between Studio and UiPath 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.
To link a Studio project to an idea in Automation Hub:
- Select the Project panel > Project Settings
> General.
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.
The 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:
