Publishing an automation project means archiving the workflow and all the other files in the folder so that it can be sent to Robots and then executed.

Automation projects can be published to Orchestrator, a custom NuGet feed or locally. After publishing to Orchestrator, the archived project is displayed in the Packages page. From here you can distribute it to other Robots, by assigning the package to an environment (creating a process).

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.

Publishing projects locally requires you to provide a path on the local machine, different than the location where process packages are published. From here, you can later manually send the packages to the Robots, so they can be executed. The default local publish location is %ProgramData%\UiPath\Packages.

This can be easily done by using the Publish button on the Design ribbon tab. Please note that automation projects cannot be published if the project.json file is located in a read-only location.

📘

Important!

Currently, you cannot execute StudioX projects from Orchestrator. If StudioX is licensed locally and the Robot is not connected to Orchestrator, you can publish your projects to the Robot Defaults and execute them from the Robot.

To publish an automation project:

1. Create a new project.
2. In the Design ribbon tab, click Publish. The Publish Project window opens.
3. In the Publish Location section, select where to publish the project:
   • Orchestrator - If the Robot is connected to Orchestrator, sends the package to Orchestrator.
   • Robot Defaults - If the Robot is not connected to Orchestrator, saves the package to the default folder for publishing locally %ProgramData%\UiPath\Packages.
   • Custom - Publishes to a custom NuGet feed or to a folder on the local machine.
4. In the Release Notes section, enter details about the version and other relevant information. Release notes for published projects are visible in the Packages section in Orchestrator. Please note that the Release Notes field accepts a maximum of 10,000 characters.
5. Add a New Version to the project, and select the Is Prerelease check box to mark the version as alpha, if needed. Please note that this automatically changes the project’s version schema to semantic. For more details about project versioning, check the About Automation Projects page.
6. Click Publish. The entire project folder is archived into a .nupkg file, and sent to the selected publish location.
7. If the project is published successfully, the Info dialog box is displayed and the project is copied to the publish location.
   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.
   • The Copy to Clipboard option.

📘

Note:

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.