- 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
- Citrix Technologies Automation
- 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
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) > Tools > Plugins.
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.
project.json file) can be added to source control from Studio. If you want to add files or folders from outside the project folder, you
must use other source control clients.
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.
