- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- About Version Control
- Managing Projects With TFS
- Managing Projects With SVN
- Workflow Diff
- 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
- Test Suite - Studio
- 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
Managing Projects With TFS
The supported versions of Team Foundation Server are:
- 2012
- 2013
- 2015
- Express 2012
- Express 2013
-
Express 2015
Note: Studio only works with Server workspaces. You cannot open projects from TFS if the workspace created by Studio is changed to a Local workspace from outside of Studio.
-
In the Team tab, click Open from TFS or Add to TFS. The Connect to Azure DevOps Server window is displayed.
-
Click Servers. The Add/Remove Azure DevOps Server window is displayed.
-
Click the Add button. The Add Azure DevOps Server window is displayed.
Note: If Studio crashes or fails to respond when you try to add a TFS server, remove the configuration files fromC:\Users\<username>\AppData\Roaming\Microsoft Visual Studio\15.0_xx\Team Explorer
, restart Studio, and try again. -
Fill in the details of your TFS repository and click OK. Your team’s collections and projects are available in the Connect to Azure DevOps Server window.
The Manage TFS Online button connects you to the web management interface.
https://<account>.visualstudio.com
) UiPath Studio requests authentication with a Microsoft account.
-
In the Team tab, click Open from TFS. The Connect to Azure DevOps Server window is displayed.
Note: The Connect to Azure DevOps Server window has the option to switch between users when connecting to the TFS repository. - Open the drop-down menu under the Select an Azure DevOps Server and pick the server you want to access. Pick a team project collection and a team project. Once the selection is made, click Connect. The Repository Browser opens.
-
In the repository browser, you can browse to and select an existing folder or copy the Selected Path.
-
Click OK to confirm the selection and close the window. The Check out from TFS project window is displayed.
To change the file and open the repository browser, use the button.
- Pick a Check out directory. The project name is added to the checkout directory by default. Click Open. The
project.json
,.xaml
and other files stored in the repository project folder are mapped locally. -
When you open a file from Studio, for example,
Main.xaml
, a Question dialog box opens with two options for pulling the file from the repository:- Check out latest and edit - opens the latest version of the
Main.xaml
file from the repository, in edit mode. The Break Lock option indicates that the file is already checkout by another user. By using this option, the lock is removed without notifying the user. -
Open local as read only - opens the local version of the
Main.xaml
file in read-only mode. The Package Manager can be opened even if the files are in read-only mode, but in order to perform changes and install dependencies, theproject.json
file needs to be checked out.Selecting the checkbox for Always checkout latest and edit and don't show me this again, and then the Check out latest and edit option propagates your choice for future occurrences. Regardless of your choice, theproject.json
file still needs to be checked out separately for certain changes to take effect.Note: If you check out only the <code>.xaml</code> file of a library project from the TFS repository, the <code>.screenshots</code> folder does not update. Use Get Latest Version on the folder to get the files.
- Check out latest and edit - opens the latest version of the
- Create or open a project in Studio. Click Start > Team > Add to TFS button, or Add to Source Control > Add to TFS shortcut in the status bar. The Connect to Azure DevOps Server window is displayed.
-
Pick the server you want to access, a team project collection, and a team project. Once the selection is made, click Connect. The Please select the folder to add under window is displayed, which allows you to select the location to add your project to.
You can browse to and select an existing folder, or click Create Folder above the left navigation pane to add a new folder. Click OK to confirm the selection and close the window.
-
The Add to TFS project window is displayed.
To add the project to a particular folder, provide a relative path to the Remote subfolder box or use the button to open the repository browser.
- Click Add. The Check in Changes window opens.
- Select the files you want to check in and write a Commit Message. Click Check In. The project files are added to the TFS repository, and checked out locally, except for the
project.json
file.
When a project is added to TFS, the context menu in the Project panel includes TFS-specific options. For more information, see Context Menu Options for SVN and TFS.
- Connect one of your projects to your TFS repository.
-
Right-click the
.xaml
file and select Check Out for Edit. The latest version of the.xaml
file is mapped locally and opened in the Project panel. It becomes locked for editing until it’s checked in. Perform any sort of changes to the files.Note: Once a file is checked out from the TFS repository, it is no longer available for check out by other users with access permissions. - Right-click the
.xaml
file or project node, and select Check In, or click the icon in the Status bar, which also counts the number of uncommitted changes. The Check In Changes window is displayed. -
Review the changes and check the Show Unversioned Files box to add imported files to the repository. Write a Commit Message to describe the changes.
- Click Check In. The latest version is now available in the repository, together with the Commit message. In Studio, the
project.json
file returns to the read-only mode. -
Click Start > Team > Disconnect to disconnect the current project from source control.
Note: If you edit a file from a project added to source control in an external editor, the change is visible in the Project panel and the status bar only after you click Refresh in the Project panel.