通知を受け取る

UiPath Orchestrator

UiPath Orchestrator ガイド

設定

[設定] ページでは、管理者が Orchestrator のテナントおよびグローバル設定を調整できます。設定をテナントごとに変更する場合は、そのテナントの [設定] ページを使用し、すべてのテナントの設定を変更する場合は、Orchestrator のホスト ポータルの [設定] ページを使用します。

ホストからの設定は、カスタム値で設定が更新されなかったすべてのテナントに適用されます。

[全般] タブ


FieldDescription
Application SettingsTime Zone - The time zone of the tenant. By default, this field is set to UTC.
The timezone list depends on the machine. To ensure that all the instances under a multi-node Orchestrator installation have the same timezone list, they must use the same operating system version.
It is recommended that the tenant and the Robots have the same time zone.

Language - The language of the Orchestrator user interface for the current tenant, including email notifications and alerts. This setting does not affect robot logs or event logs, which use your Windows language.

icon Custom header color - Select a color for the Orchestrator window header. This is useful for distinguishing between multiple Orchestrator tenants. The header color is selected by clicking the colored square to bring up your machine's color selector.

icon Custom logo - Enables you to upload your desired logo which appears in the Orchestrator window header. The accepted formats are .png and .svg, with a maximum file size of 1MB.
Note: A logo can be added at the host and/or tenant levels. The host setting will be overridden by any logo added at the tenant level.

In Automation Suite, changing the company logo is performed from the Organization Settings page. Learn more about managing organization settings in Automation Suite.
Client Binaries (Robot, Studio, Assistant) Auto-Update SettingsAuto-fill available product versions (host setting) - Configures the update policies to contain the latest versions of client binaries. If you need to manage update versions manually, disable this option and follow the steps described in this article.

Ignore auto-update status for robot machines that were offline for more than ___ days (tenant setting) - This excludes inactive machines from the update process and no longer takes them into account when the update status is reported.
Personal Workspaces (tenant setting)Enable the Personal Workspaces feature.
Note: This action cannot be reversed, once the Personal Workspaces feature is enabled it cannot be disabled.

Enable Personal Workspace - Create personal workspaces for all users in a tenant that use a certain attended licensing profile, while also selecting the UI profile to be used for those users.
Standard Roles (tenant setting)Create standard roles for modern folders. These roles empower you to leverage the benefits of user groups.

Click Create Role next to each of the roles you want to be automatically created.
Modern FoldersEnable the Account-Machine Mappings feature.
Classic FoldersActivate Classic Folders - Enable classic folders.
Note: Use this setting with caution, since classic folders are disabled and will soon be deprecated.
Email SetupEnable alerts email.
For more information, see Setting Up Email Alerts.

[デプロイ] タブ


Enables you to configure and secure feeds for packages and libraries. You can manage the feeds for all tenants from a centralized location using Automation Ops. For more information, see feeds management in the Automation Ops guide.

ここでの設定は、テナント フィードにのみ影響します。フォルダー フィードと個人用ワークスペース フィードは常に内部フィードであり、各フォルダーまたは個人用ワークスペースのコンテキストでのみ使用できます。

パッケージ

オートメーション パッケージを維持できる内部フィードまたは外部フィードを設定できます。既定では、内部フィードが使用されます。基本認証の資格情報を定義するか、API キーを使用して、フィードのセキュリティを保護できます。

FieldDescription
InternalMust be selected in order to use an internal feed. The feed can be secured either with the Secure Deployment option or by using an API key.
ExternalMust be selected in order to use an external feed. The feed can be secured either by using an API key or basic authentication credentials.
Deployment URLOnly available if External is selected.
The address where the NuGet feed is located.
Secure DeploymentEnsures that your automation packages are downloaded through a secure NuGet feed.
API KeyThe key used to secure your feed against write operations such as delete or upload.
AuthenticationOnly available if External is selected.
Specify the credentials for your basic-authenticated feed.
Please keep in mind that both the user name and the password used with the API Key option should be used in this case as well.

ライブラリ

ライブラリ パッケージとの連携時に使用されるフィードを設定できます。ライブラリは Studio からパブリッシュすることも、Orchestrator でユーザーが手動でアップロードすることもできます。どちらの場合も、選択したフィード内にライブラリが格納されます。

FieldDescription
Only host feed (tenant setting)Libraries are stored in the host feed and are available to all tenants which use it. The Libraries page is the same for one Orchestrator instance, meaning libraries are not isolated at the tenant level: each tenant has access to the other tenants' activity.
🛈 You cannot upload libraries from Orchestrator if this option is selected.
🛈 This option gives robot access to the host feed only.
Only tenant feed (tenant setting)Libraries are isolated at the tenant level, meaning data is separated across tenants. You may set an internal or an external feed in which libraries are maintained. By default, an internal feed is used.
🛈 This option gives robot access to the tenant feed only.
Both host and tenant feeds (tenant setting)Libraries are isolated at the tenant level, meaning data is separated across tenants. You may set an internal or an external feed in which libraries are maintained. By default, an internal feed is used.
🛈 This option gives robot access to both the host and tenant feeds.
InternalNot applicable if Only host feed is selected.
Must be selected in order to use an internal feed. The feed can be secured either with the Secure Deployment option or by using an API key.
ExternalNot applicable if Only host feed is selected.
Must be selected in order to use an external feed. The feed can be secured using an API key.
Secure DeploymentNot applicable if Only host feed is selected.
Ensures that your automation packages are downloaded through a secure NuGet feed.
Deployment URLNot applicable if Only host feed is selected and only available if External is selected.
The address where the NuGet feed is located.
API KeyNot applicable if Only host feed is selected.
The key used to secure your feed against write operations such as delete or upload. The user can use it to publish packages.
This key is generated by the external provider and has the following format [username]:[password]. For example, admin:2652ACsQhy.

プロキシサーバー経由で外部フィードを使用する場合の前提条件

Windows 上でプロキシサーバーを設定した状態で外部フィードを使用する場合は、あらかじめ次の手順を行っておく必要があります。

  • Orchestrator のアプリケーション プール ([インターネット インフォメーション サービス] > [アプリケーション プール][ユーザー プロファイルの読み込み]) オプションを True に設定します。
436
  • アプリケーション プール ID アカウント (NuGet.config) に関連付けられた C:\Users\[YourAppPoolIdentityAccountName]\AppData\Roaming\NuGet\NuGet.Config ファイルに使用したプロキシ設定を追加します。
<config>
<add key="http_proxy" value="http://ipaddress:port" />
</config>

📘

Note that deployment settings are loaded only when the Robot Service connects to the server. Whenever they are modified you need to restart the UiRobotSvc service for the changes to take effect.

[セキュリティ] タブ


Robot

FieldDescription
Run Disconnected HoursSpecify the number of hours a Robot can run offline, without checking for its Orchestrator license. By default, it is set to 0. The maximum accepted value is 168 hours. This setting does not apply to Studio.
Allow both user authentication and robot key authentication (tenant settings)When connecting the robot to Orchestrator allow both standard connections with tokens that don't expire and connections with tokens that expire.
The Sign in option is displayed in the Assistant allowing users to connect Studio and the Assistant to Orchestrator using their credentials.
Enforce user authentication, disable robot key authentication (tenant setting)Only available if Allow both user authentication and robot key authentication is selected.

When connecting the robot to Orchestrator allow only connections with tokens that expire. User login is required to make Orchestrator HTTP requests, run Attended Robots, or view processes in the Assistant.
Restrict attended robot authentication in the Assistant to interactive user sign-in.

Warning!: Secure authentication requires recompiling the workflows that use Orchestrator activities or make direct HTTP calls to the Orchestrator API utilizing v2020.10 activity packages or higher.

[拡張性] タブ


Robot サービスが Orchestrator の SignalR チャネルをサブスクライブするかどうかを指定したり、最適なトランスポート プロトコルを設定したりします。これらの設定はアップグレード時に保持されます。

1570

SignalR (Robot)

FieldDescription
EnabledThis toggle specifies if the Robot service subscribes to Orchestrator's SignalR channels or not. By default, this setting is enabled, and all available channels are selected:
WebSocket
Server-Sent Events (SSE)
Long Polling

When all transport channels are enabled, the best available transport is automatically selected, in the following priority order: WebSocket > Server-Sent Events > Long Polling. If the first protocol is not available for any reason, the next in line (if enabled) is used to facilitate the communication between Orchestrator and Robot.
WebSocketWhen selected, enables the WebSocket transport protocol to be used to connect the Robot to Orchestrator's SignalR channels. This is the highest protocol used in the order of priority due to its performance and support for simultaneous communication in both directions - from the Robot service to Orchestrator and vice versa.

If the SignalR (Robots) feature is not enabled, WebSocket becomes the only available transport protocol.
Server-Sent Events (SSE)When selected, enables the Server-Sent Events (SSE) push technology to be used to connect the Robot to Orchestrator's SignalR channels. This is the first backup in case WebSockets is not available for any reason.

This option cannot be used if the SignalR (Robots) feature is not enabled.
Long PollingWhen selected, enables the long polling transport protocol to be used to connect the Robot to Orchestrator's SignalR channels. This protocol is used in case the WebSockets and SSE ones are not available.

This option cannot be used if the SignalR (Robots) feature is not enabled.

[非稼働日] タブ


テナントレベルの機能。

トリガーの実行を制限する、非稼働日のリストをテナントごとに定義できます。つまり、祝日や土日など、通常の業務がない日には、長期スケジュールがトリガーされないように設定できます。定義された非稼働日を過ぎると、通常どおりにトリガーされるようになります。

これらの制約をトリガーに適用するには、トリガー設定時に非稼働日カレンダーを選択する必要があります。[非稼働日] タブで加えたすべての変更は、そのカレンダーを使用するすべてのトリガーに影響を与えます。

📘

注:

テナント レベルで設定されているタイムゾーン ([設定] > [全般]) とは異なるタイムゾーンのトリガーについては、[非稼働日制限] が無効化されます。タイムゾーンが明示的に定義されていないテナントは、ホストからタイムゾーンを継承します。

非稼働日の管理方法の詳細については、こちらをご覧ください。

1 日前に更新


設定


改善の提案は、API リファレンスのページでは制限されています

改善を提案できるのは Markdown の本文コンテンツのみであり、API 仕様に行うことはできません。