Create a process from package using Orchestrator API

Hi,
We are looking at creating a CI/CD pipeline and have found these links:

It seems that will get as far as deploying the package but not create a process of update any existing processes to use the newer version of the package.

What we are not clear on is the following:

  1. if a process can be created (if first time package is published) using Orchestrator API ?

  2. Can every processes be updated automatically in Orchestrator using the API, when an updated version of package is uploaded via CI/CD pipeline? I believe depending on the robot type it will automatically download the latest version if a newer one is available.

Any help is appreciated.

Anyone have any thoughts on this one?

Hello!

Yes, you can do those operations via Orchestrator API.

if a process can be created (if first time package is published) using Orchestrator API ?

It’s possible to create Processes using the POST ​/odata​/Releases endpoint. For that, you need data like the Package’s key (represented by the field ProcessKey) and Package’s version (represented by the field ProcessVersion). If you are creating the Process in a Classic Folder, it’s also necessary to specify data about Environment.
Although a bit confusing, note that, in the API, Processes are referred to as Releases, and Packages are referred to as Processes.

Can every processes be updated automatically in Orchestrator using the API, when an updated version of package is uploaded via CI/CD pipeline? I believe depending on the robot type it will automatically download the latest version if a newer one is available.

You can use the endpoint POST ​/odata​/Releases({key})​/UiPath.Server.Configuration.OData.UpdateToLatestPackageVersion to do that. If you need to update to a specific version, then there’s POST ​/odata​/Releases({key})​/UiPath.Server.Configuration.OData.UpdateToSpecificPackageVersion.

More details about these endpoints are available in Orchestrator’s Swagger page or in the documentation: https://docs.uipath.com/orchestrator/reference/about-odata-and-references#api-references