- 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
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScaleCoordinates Migration Tool
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- StudioPro
- Extensions
- Troubleshooting
About Version Control
Source control systems prove very handy when developing larger projects that require smooth collaboration between multiple users. You can connect Studio automation projects to GIT, SVN, or TFS by accessing Home (Studio Backstage View) > Team.
The source control plugins for GIT, SVN, and TFS are enabled by default in Studio. You can enable or disable them individually from Home (Studio Backstage View) > Settings > Team.
When a project is open in Studio, the Add to Source Control button in the status bar offers shortcuts to GIT Init, Copy to GIT, Add to TFS, and Add to SVN.
.local
subfolder is ignored by default). In addition, make sure there are no ignore lists such as .gitignore
files configured in a way that excludes project files and subfolders.
The GIT Version Control offers an overview and instructions on how to work with GIT-versioned projects in Studio.
The steps for checking in your projects to a TFS or SVN repository are detailed in the dedicated pages Managing Projects with TFS and Managing Projects with SVN.
Part of working with versioned files is the possibility to compare changes between the local version of the file and the one checked in the repository. You can do so using Workflow Diff.
If you want to compare two similar files in the same automation project, use Compare Files, which is also available for unversioned files.