流程表示链接到特定文件夹的包版本。部署新流程时，该流程将对所有有权访问该文件夹的帐户可用。
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.
除了从“流程”和“作业”页面执行流程外，您还可以将任何流程配置为在启动机器人代理时自动启动。作为管理员，这使您可以确保启动必要的流程而不会受计算机用户影响而延迟或失败，例如，确保遵守公司的 IT 策略。
The table below displays field descriptions for the Processes page.
| Field | Description |
|---|---|
| Name | The display name of the process. The process type is illustrated with an icon displayed alongside the version. The icon represents the type of that specific process version. Requires User Interface  Background Process  You can sort the processes list by Name. |
| Package Name | Not visible by default. To display the column, select it from the Columns menu. The name of the package that was deployed. You can sort the processes list by Package Name. |
| Version | The number of the package version currently being used in a given process. The  icon next to this field indicates that you are not using the latest available version.If the package version associated with a process is no longer available in the configured NuGet repository, it is indicated with the following icon  .If you are using the latest available version, the following icon  is displayed. |
| Environment | Available only for classic folders. The name of the environment assigned to a given package. |
| Job priority | The priority of the job. Click here for details about the job prioritization mechanism. You can sort and filter the processes list by Job priority. |
| Scope | Not visible by default. To display the column, select it from the Columns menu. The scope of a project, set at design time in Studio. The following options are available: Process - displayed for Studio projects of type Process or Library Testing - displayed for Studio projects of type Test Automation You can filter the processes list by Scope. |
| Execution type | The type of the process execution. Linked to the Attended Automation project setting in Studio: if you turn on the toggle, the process is executed in an Attended context if the toggle is off, the process is executed in an Unattended context The Unspecified value is displayed for packages published prior to the 2021.10.3 Studio version. Click here for details about the Attended Automation. |
| Compatibility | The compatible operating system for the underlying target framework of the automation project. Click here for details about the process compatibility. |
| Entry point | The workflow file used to start the execution of the process. By default, the Main.xml file is set as the entry point. If your project contains multiple entry points, the one selected at process creation is displayed.Click here for details about the entry point. |
| Description | A custom description for the process. It is recommended that you populate this field, especially when dealing with multiple users and processes in Orchestrator. |
运行时参数
入口点
There are cases when your automation projects consist of multiple workflows. For such projects, it is a good practice to hold your project's main workflow in the Main.xaml file. All other automation .xaml files included in the project should be linked to the Main.xaml through the Invoke Workflow File activity since in typical scenarios only the Main.xaml file is executed when you run a job, it being the default entry point of any automation project. Learn more about project organization and design principles in Studio.
您可以更改自动化项目的入口点，即通过更改主 .xaml 文件来更改其执行“门”。同样，您可以为 RPA 流程添加多个入口点，从而仅执行自动化项目的某个分支。
您可以更改 .xaml 文件或在 Studio 中为 RPA 流程添加多个入口点，方法是右键单击不同的 .xaml 文件并将其设置为主文件或将其添加为入口点。
重要
此功能仅适用于无人值守的执行，即从 Orchestrator 启动的作业。使用 Assistant 启动作业时，无论在 Orchestrator 中设置的入口点如何，机器人都将执行设计时在 Studio 中设置的主入口点。
假设您建立了一个检查发票的工作流。发票可以从云存储中下载，也可以位于您的设备上。
您在项目内部设计了两个工作流，并将它们都设置为入口点：
DownloadInvoiceFromStorage.xaml- 从外部存储下载发票的工作流GetInvoiceFromLocal.xaml- 从您的设备获取发票的工作流。
在 Orchestrator 中的运行时，您可以选择与场景相对应的工作流作为入口点。如果发票已在本地设备上，则将 GetInvoiceFromLocal.xaml 设置为入口点。这样一来，将从该步骤开始执行，并继续进行发票检查工作流（Main.xaml 文件）。
注意
对于 2020 年 7 月之前发布的包，Orchestrator 无法确定主入口点，因此默认情况下不选择任何入口点。您需要从下拉列表中手动选择入口点。
如果流程不支持多个入口点，则 Orchestrator 在“入口点”下拉列表中显示
Default，并禁用该字段。
In、Out、In/Out 参数
通过在 Studio 中设计项目，使其接受 In 或 Out 参数，您便可在其他第三方应用程序或 Orchestrator 中使用这些参数。这意味着您创建的任何流程都可以通过 Orchestrator API 或接口接收输入参数。
在 Orchestrator 中，参数和相关信息显示在多个位置：专用参数部分（“运行时参数”或“参数”选项卡）中的流程级别、作业级别和触发器级别。
You can specify values for any input arguments. For more info on input and output arguments in Orchestrator, please visit this page.
1 - 选择入口点。仅在有多个入口点可用时启用。
2 - 根据方向（输入、输出、全部）筛选显示的参数
3 - 查看设置为入口点的 .xaml 的参数和相关信息。
注意
在任何级别，为 Studio 中的输入参数提供的默认值都不会显示在 Orchestrator 中。
后台流程与前台流程
This section describes existing process types according to the user interface requirements. The process type is configured in Studio on the Project Settings window and illustrated accordingly in Orchestrator after publishing the project.
根据用户界面要求，有两种类型的流程：
- Background Process - Does not require a user interface, nor user intervention to get executed. For this reason, you can execute multiple such jobs in unattended mode on the same user simultaneously. Each execution requires an Unattended/NonProduction license. Unattended robots handle background processes in Session 0, under
NT AUTHORITY\LOCAL SERVICE, which has no UI and cannot interact with a user session.
Learn more about background process automation in Studio. - Foreground Process - Requires user interface as the execution needs the UI to be generated, or the process contains interactive activities, such as Click. You can only execute one such process on a user at a time.
注意
同一个用户可以同时执行多个后台流程和单个前台流程。
下表显示了根据机器人凭据注意事项运行前台/后台流程所需的 UiPath Robot 版本。
| Process type | Credential considerations | Robot version |
|---|---|---|
| Background | Robot with credentials | Any |
| Foreground | Robot with credentials | Any |
| Background | Robot without credentials | 2021.10+ |
| Foreground | Robot without credentials | Invalid configuration! Jobs cannot be executed. |
流程兼容性
在 Studio 中创建自动化项目时，开发者必须配置一个会影响该自动化项目和兼容操作系统的基础目标框架的兼容性属性。
下表显示了需根据流程的目标框架和操作系统兼容性执行流程的 UiPath 机器人版本。
详细了解 Studio 中的目标框架。
| Target framework | Operating system | Robot version |
|---|---|---|
| .NET Framework 4.6.1 | Windows - Legacy | Any |
| .NET 5.0+ | Windows | 2021.10+ |
| .NET 5.0+ | Cross-platform | 2021.10+ |
版本管理
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. For more information, see the Managing Package Versions page.
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. For more information, see the Managing Package Versions page.
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.
流程权限
创建流程：
- 查看包的权限；
- 查看和创建流程的权限。
从“流程”页面启动作业：
- 创建流程所需的权限
- 创建作业
在传统文件夹中部署流程：
- 创建流程所需的权限
还需要查看环境的权限。
阅读有关角色的更多信息。
约一个月前更新