A process is a deployed and configured state of a package, ready to be executed as a job.

More specifically, a process represents a package version linked to a particular folder. When you deploy a new process, it becomes available for all accounts 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 accounts 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 ensure that necessary processes are launched without delay or failure from the machine user, for example, to ensure adherence to company IT policies.

The following table contains column descriptions for the Processes grid.

For projects with multiple workflows, use Main.xaml as your main workflow and link other .xaml files through the Invoke Workflow File activity. Learn more about project organization in Studio.

You can change or add entry points to control which workflow executes. In Studio, right-click a .xaml file and set it as main or add it as an entry point.

You have two workflows to process invoices from different sources:

At runtime in Orchestrator, select the entry point that matches your scenario. If the invoice is already local, select GetInvoiceFromLocal.xaml to start execution from that workflow.

Designing your project in Studio to accept In or Out arguments enables you to use them in other third-party apps or Orchestrator. This means that any process you create can receive input arguments through the Orchestrator API or interface.

In Orchestrator, arguments and related information are displayed in multiple places: at the process level, job level, and trigger level in the dedicated arguments sections (Runtime Arguments or Arguments tab).

You can specify values for any input arguments. For more info on input and output arguments in Orchestrator, please visit this page.

Figure 1. Process configuration

Figure 2. Arguments

Processes are classified by their user interface requirements.

Background processes don't require a user interface or user intervention. You can execute multiple background jobs simultaneously on the same user in unattended mode. Each execution requires an Unattended/NonProduction license. Unattended robots run background processes in Session 0 under NT AUTHORITY\LOCAL SERVICE, which has no UI access.

Learn more about background process automation in Studio.

Foreground processes require user interface access (either for UI generation or interactive activities like Click). You can execute only one foreground process per user simultaneously. However, the same user can execute multiple background processes and one foreground process at the same time.

The process type is set in Studio on the Project Settings window and appears in Orchestrator after publishing.

Figure 3. Starting a process in background

The following table shows the UiPath® Robot version required to run foreground/background processes according to the robot credential considerations.

When creating an automation project in Studio, developers must configure a compatibility attribute that impacts the underlying target framework of the automation project and the compatible operating system.

Figure 4. Process compatibility

The following table shows the UiPath Robot version required to execute processes according to their target frameworks and OS compatibility considerations.

If a new version of a package is available in Orchestrator (you published a new version from Studio), it is indicated with the icon next to the process it is part of.

You may update processes to the latest available version individually, on the corresponding View Processes window, or you may update them in bulk, by selecting multiple of them and clicking the global Use Latest button.

If a package version associated with a process is no longer available in the configured NuGet repository, it is indicated with the icon.

If you are using the latest available version of a package in a specific process, the icon is displayed next to the process.

Windows applications that are used by the underlying Studio package are displayed in the Applications section, as relevant to the selected package version.

If the package uses applications that cannot be identified, an Unknown apps entry is displayed, suffixed by the number of unidentified apps, in parentheses.

If no applications can be retrieved, a No app(s) could be retrieved for this package message is displayed. This is most likely due to one of the following reasons:

These details are also displayed in the Show release notes window for each package version.

Creating a process:

Starting a job from the Processes page:

Read more about roles.