- 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

Studio User Guide
Project Dependencies Mass Update
linkThe Project Dependencies Mass Update Tool is used for updating dependency packages and their runtime rules in multiple automation projects, stored locally or in source control repositories.
The wizard can be accessed both from Studio Backstage view and command line. Please note that the Project Dependencies Mass Update Tool from Studio Backstage view cannot be used for removing dependencies from the project.
Please note that when using the Project Dependencies Mass Update Tool, you implicitly accept the license terms of each package version that you update.
It is recommended to save and close projects from Studio, before making changes to them using the Project Dependencies Mass Update Tool.
Mass Updating Projects
link- In Studio Backstage view -> Tools, click on the Project Dependencies Mass Update Tool icon. The Project Dependencies Mass Update window opens at the Choose Feeds step.
- The Choose Feeds step shows all default and custom package feeds configured in Studio. Select the check box next to the feeds that contain the needed dependency versions.
- Click Next. The Select Dependencies step is displayed.
- Similar to the Manage Packages window, use the search bar in the Select Dependencies tab to find a specific dependency version. Select the Include Prerelease check box to view intermediary versions.
- Click Next. The Get Repository step is displayed.
- The All Dependencies tab displays the list of all packages available on the previously selected feeds.
- The Selected Dependencies tab shows the list of dependencies to be updated in the project.
- At the Get Repository step, select the location of your projects:
- Local - Enter a local path or click Browse
to select one.
- GIT - Enter the repository URL. After you click Next, you are prompted to select a branch. If authentication is required, you are also prompted to provide your credentials.
- TFS - Enter the repository URL or click Browse
to connect to a server and browse through TFS projects.
- SVN - Enter the repository URL. For password-protected SVN repositories, you are prompted to authenticate with a username and password, if no previous authentication was performed.
- Local - Enter a local path or click Browse
- Click Next. The Filter Projects step is displayed.
- In the Filter Projects tab, select at least one project from the list by checking the box next to the project name.
- Click Next. The Commit step is displayed.
- In the Commit tab, write a message detailing the changes made to project dependencies. To skip this tab, simply select the Skip Step check box.
- Click Next. The Publish step is displayed.Note: The Commit tab opens only if you've connected to GIT, SVN, or TFS in the Get Repository tab.
- In the Publish tab, select a location for publishing the modified projects, either Orchestrator, a custom feed or locally. The project version auto increments. To skip this step, simply click the Skip Step check box.
- Click Confirm to publish the modified project as a
.nupkg
file. The Results tab is displayed. - The Results step shows details about the updated dependencies, as well as the projects that failed.
The Added Dependencies category shows the updated version of the package, while the Removed Dependencies category mentions the previously installed version.