- 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
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- 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
- Studio testing
- 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
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected

Studio User Guide
Creating a Basic Library
linkThe following tutorial walks you through the steps of creating a library in Studio, publishing and using it in other automation projects.
Creating a library is similar to Creating a Basic Process. The difference is that a library is a package containing reusable components which can be used in the context of other projects.
This example gets data from an Excel spreadsheet and appends it to another Excel file. Next, it walks you through the steps for packaging and publishing the project to a custom feed, installing the package to another project, and using the activity it contains.
This example uses Excel activities that do not require Microsoft Excel to be installed on your machine.
Let’s begin.
Creating a Library
link- Launch Studio. In the HOME Backstage view, click Library to create a new library project. The New Blank Library window is displayed.
-
Type a name for the project, use QuickLibrary for this example. Add a brief
description and pick a location.
Note: The project name cannot exceed 128 characters, and the description cannot exceed 500 characters.
- Click Create. The new library is opened in Studio.
Adding Excel Activities
link- In the Activities panel, search for the Excel Process Scope activity and drop it to the Designer panel.
- Add a Use Excel File activity to the sequence. This activity is required for most of the Excel-related activities.
- In the Excel file field, browse to the Excel file from which you want to get the data. Optionally, you can usethe Reference as field to change the way this file is referenced throughout the workflow (
Excel1
in this case). - Add a second Use Excel File activity inside the first Use Excel File activity and browse to the Excel file where you want to copy the data. Add an optional reference to this second file (
Excel2
in this case). - Add a Copy/Paste Range activity.
- In the Source field, select the Plus
button to indicate the name of the sheet in the first workbook. For this example, the field should read
Excel1.Sheet("Sheet1")
. - In the "Destination" field, select Plus
to indicate the name of the sheet in the second workbook (
Excel2.Sheet("Sheet1")
in our case). Your project should look like in the image below. - In the ribbon, click Run File or use Ctrl + F6 to execute the workflow. The data gathered from the first Excel spreadsheet is copied to another.
Packaging a Library
link.nupkg
file by publishing the project.
- Open the library project in Studio.
- From the ribbon, click the Publish button. The Publish Library window opens.
- In the Package properties tab, enter a package name. In the Release Notes field, add a few details about the library. This is useful for tracking the changes made to the library in each new published version.
- In the Publish options tab, select Publish to > Custom, and then, in the Custom URL field, add the path to a local folder. For example, you can create a
myfeed
folder on your Desktop.
- Click Publish. The package is now available in the local folder as a
.nupkg
file.
Installing Reusable Components
linkTo use the package in another project, you first need to add it as a project dependency. To get started, create a new Process in Studio, as explained in the Creating a Basic Process page.
Read more about project dependencies in the About Dependencies page.
Adding a Custom Feed
- In the Studio ribbon, click Manage Packages > Settings. The default and user-defined feeds are displayed.
- In the User defined packages sources container, add a name for your feed in the Name field. In the Source field, add the path to the folder where you published your library to.
- Click Add. Your new feed is added to the section.
You need to follow the above steps whenever you want to add or remove a user-defined feed in Studio. Check out the About Activities Packages to read more information about activities feeds.
Installing the Package
- In the Manage Packages window, go to the previously added feed under the All Packages tab on the left. The list of packages available on the feed is displayed.
- Search for the package and select it. In our example, the package name is QuickLibrary.
- Click Install, then Save. The package is now installed in your project, and visible in the Project panel, under Dependencies.
Adding Activities From the Library
- In the Activities panel, search for the name of the package, in our case
Quick Library
. - Drop the activity in the Designer panel.
- In the Studio ribbon, click Run File or use Ctrl + F6 to execute the activity.
You can add other activities like Copy Sheet or Auto Fill Range, but these require Microsoft Excel to be installed on your machine.
The advantage of reusable components is that they reduce repetition. You create them once and reuse them in other projects.
To download the library we created above, click the button below: