About Processes

A process represents the package version linked to a particular folder. When you deploy a new process, it becomes available for all the users that have access to that folder.

The Processes page enables you to deploy an uploaded package as a new process, manage previously created processes, keep all your processes up to date with the most recent package versions, and directly start a job using the desired process. This helps you distribute packages across all users and robots in your organization and execute processes faster, whether from the Processes or Jobs page.

In addition to executing processes from the Processes and Jobs pages you can also configure any process to automatically start when the Robot agent is launched. As an administrator, this enables you to be sure that necessary processes are launched without delay or failure from the machine user, for example to ensure adherence to company IT policies.

Note that creating a process requires your user to have View permission on Packages, and View and Create permissions on Processes. You also need Create on Jobs to instantly start a job from the processes page. For deploying processes in classic folders, View on Environments is also required.

In the aforementioned window you can view both input and output parameters, their name and type, and whether their value is inherited from the package or they have no default value. Last but not least, you can specify values for any input parameter. For more info on input and output parameters in Orchestrator, please visit this page.

Activities used in Studio packages are stored in a NuGet feed that Orchestrator has access to. As a result, each time you deploy a package to an environment, the activities are also sent to the Robot machines that are part of that environment. This enables you to execute processes using those Robots, even when your connection to Orchestrator is down.