- 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
- Automating Citrix Technologies
- 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
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
About Publishing Automation Projects
Publishing an automation project means archiving the project folder so that it can be sent to Robots and then executed.
By default, all the files in the project folder are published except for test cases. If you want to prevent a specific file from being included in the published package, right-click it in the Project panel, and then select Ignore from Publish (not available for workflow files in library projects). In the case of libraries, to prevent a workflow file from appearing as a reusable component in the Activities panel when the published library is installed in a project, right-click it in the Project panel, and then select Make Private.
You can publish automation projects to Orchestrator, a custom NuGet feed, or locally. After publishing to Orchestrator, the archived project is displayed on the Packages page and you can create a process to be distributed to Robots. When you publish an automation process to the Orchestrator Personal Workspace or you publish test cases, a process is created automatically if one does not already exist, and existing processes are automatically updated to the latest published version.
Additionally, automation projects may be published to a custom NuGet feed, with the option to also add an API key if the feed requires authentication.
%ProgramData%\UiPath\Packages
.
project.json
and design.json
files in the project folder must not be in a read-only location (for example, if the project is under source control, the
files must be checked out for editing).
You can publish projects from Studio or from the command line. To update dependencies for multiple projects and publish them all at once, use the Project Dependencies Mass Update Tool.
To publish a project, select Publish in the Studio Design tab ribbon.
To publish an automation project:
The Info dialog box displays:
- The name under which the package was published.
- The version number under which the package was published;
- The location where the project was published if the project was published locally or in the Robot's Default. Click the path to go to the package, except if the publish location was Orchestrator.
- The Details option which expands a list containing the names of project files that were published.
-
The Copy to Clipboard option.
Information added during publishing, like the publish location is persisted in the window, so it can be used for subsequent publish actions performed for the same type of project. Each time you click Publish, a new version of the project is created and sent to the packages feed. Publishing to a secure feed can be authenticated either through the Robot Key, Orchestrator credentials, Windows authentication, or API key.
.xaml
file in
Studio, perform the changes, and then publish the project again.
You can publish projects using the UiPath.Studio.CommandLine.exe publish command.
UiPath.Studio.CommandLine.exe is available in the installation folder:
- For per-machine installations, the default path is C:\Program Files\UiPath\Studio\.
- For per-user installations, the default path is %localappdata%\Programs\UiPath\Studio\.
The following arguments are available for the publish command:
Argument | Description |
---|---|
-p, --project-path | The path to the project.json to publish. The argument is mandatory. |
-g, --target |
Where to publish the project:
|
-f, --feed | The custom URL for publishing the project. This can also be a custom local directory, similar to the path in the Publish options tab in Studio. |
-a, --api-key | The API key for publishing the project. This argument can be used for a custom target. |
-i, --icon | Path to the custom icon to use for the package. |
-n, --notes | Release notes that contain changes brought to the project. |
-v, --new-version | The new version for the project. If not provided, the version is automatically incremented. |
-t, --timeout | Specifies the timeout value for publishing projects. The default timeout is 30 seconds. This setting only applies for the package transfer to Orchestrator duration. |
--cer-path | The local path to the certificate for package signing. |
--cer-password | The password for the certificate. |
--timestamper-url | The URL to the timestamper. |
--incl-all-feeds | Not required. |
--help | View the arguments available for each command. |
--version | Check the version of UiPath.Studio.CommandLine.exe. |
For example:
-
The following command publishes the Sample process to the Orchestrator Tenant Processes Feed:
UiPath.Studio.CommandLine.exe publish --project-path "C:\Users\username\Documents\UiPath\Sample\project.json" --target OrchestratorTenant --notes "Fixed a couple of bugs."
-
The following command publishes the same process to a local folder:
UiPath.Studio.CommandLine.exe publish --project-path "C:\Users\username\Documents\UiPath\Sample\project.json" --target Custom --feed "C:\Users\username\Desktop\myfeed" --notes "Fixed a couple of bugs."
For more information about the CommandLine.exe utility, see Mass Update Command Line Parameters.