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
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.
Files that are not created during the execution of the automation project become read-only when published to Orchestrator. As a result, you can only read them, and not write to them when starting the process from Orchestrator. If your business process requires you to write to a specific file at some point, be sure to create it during the execution of the package.
To publish an automation project:
- In Studio, create a new project.
- In the Design ribbon tab, click Publish. The Publish Project window opens.
- In the Publish Location category, set the project to be published to Orchestrator, a custom NuGet feed or on the local machine.
- Type in the Release Notes, which are later visible in the Packages section in Orchestrator. Add a New Version number and click Publish. The entire project folder is archived into a
.nupkgfile, and uploaded to Orchestrator, the custom NuGet feed or saved in the local directory.
The default version number generated for the project has the format M.m.bbbb.rrrrr, where:
- M is the major version.
- m is the minor version.
- bbbb is the build version.
- rrrrr is the revision version.
The major and minor versions can be edited in the
project.json file also, while the build and revision versions are generated according to an algorithm - the build value is the number of days that elapsed since 01.01.2000. The revision value is the number of seconds which elapsed in the current day, until the moment of the release. The result is divided by 2, so that the maximum revision number does not exceed 65535.
- If the project is published successfully, the Info dialog box is displayed and the project is copied to the NuGet location set in the
NuGetServerUrlparameter, in the
The Info dialog box displays:
- The name under which the package was published to Orchestrator, in the Packages page, or locally;
- 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.
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.