- 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
Project Templates
Project templates can speed up automation design when used as a starting point for new automation projects. You can use one of the built-in templates or use custom templates from other sources, such as the organization-wide template feed. In addition, you can create and publish your own custom templates.
The following built-in project templates are available on the Start tab in Studio Backstage View:
- Background Process
- Mobile Testing Project
- Orchestration Process
- Robotic Enterprise Framework
- Trigger Based Attended Automation
-
Note:
If after updating Studio from a version prior to 2021.4 you experience issues such as no built-in templates being displayed on the Start tab or pinning/unpinning templates not working, do one of the following, and then restart Studio:
- Open the file
C:\Users\<user>\AppData\Roaming\UiPath\UiStudio.v2.settingsin a text editor and set the value of the<HasCustomFavorites>element tofalse. - Go to Settings > General and select Reset settings. For more information about the settings that are reset, see Configuring Studio Settings.
- Open the file
To browse and search for custom templates from all available sources, go to Home (Backstage View) and select the Templates tab.
User-defined processes, or test automation projects can be saved as templates to be used in other automation projects. Such templates may contain a particular set of dependencies and built-in workflows with already defined variables and arguments that can later be used in various projects.
Studio offers two ways to create your own custom templates, either by using the Template project type in the Home tab or by exporting a process, or test automation project as a template.
- In the Studio Backstage view, under New Project, click Template.
- Enter the template name and description, and the location where to create the template.
-
Choose between a Process and a Test Automation type of template, and pick a language between Visual Basic and C#.
-
Click Create and your template opens in Studio.
Processes and test automation projects can be exported as templates, published to a certain location, and then made available in the Templates tab in Studio's Backstage view.
A process, test automation, or modified built-in template opened in Studio can be exported using the Export as Template ribbon button.
When exported, the template is saved under the path in the Location field.
Publishing templates is similar to publishing processes and libraries, with the exception that the wizard contains an additional step where to enter template information. For more information, see About Publishing Automation Projects.
You can view all available project templates in the Templates tab in Studio Backstage View.
Recently used templates are listed at the top. You can search for templates by name and description, select whether to include prerelease versions, or filter templates by location.
The following template locations are available:
- All - All locations.
- Built-in - Templates that come installed with Studio.
- Official - Templates from the official UiPath feed.
- Orchestrator - Organization-wide templates feed, available when connected to Orchestrator.
- Local - The local user feed, by default:
C:\Users\User\Documents\UiPath\.templates. The location can be defined by selecting Settings > Locations in Studio Backstage view. - Marketplace - Templates published to the UiPath Marketplace.
