Auf der Seite Einstellungen können Administratoren Mandanten- und globale Einstellungen für Orchestrator anpassen. Nehmen Sie die Änderungen pro Mandant vor, indem Sie die Seite „Mandanteneinstellungen“ verwenden, oder für alle Ihre Mandanten, indem Sie die Seite Einstellungen im Orchestrator- Hostportal verwenden.
Hosteinstellungen gelten für alle Mandanten , die ihre Einstellungen nicht mit benutzerdefinierten Werten aktualisiert haben.
Registerkarte „Allgemein“
| Field | Description |
|---|---|
| Application Settings | Time 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.  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. 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 Settings | Auto-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 Folders | Enable the Account-Machine Mappings feature. |
| Classic Folders | Activate Classic Folders - Enable classic folders. Note: Use this setting with caution, since classic folders are disabled and will soon be deprecated. |
| Email Setup | Enable alerts email. For more information, see Setting Up Email Alerts. |
Registerkarte „Bereitstellung“
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.
Einstellungen hier wirken sich nur auf Mandantenfeeds aus; Ordnerfeeds und Feeds des persönlichen Arbeitsbereichs sind immer intern und im Kontext des jeweiligen Ordners oder des persönlichen Arbeitsbereichs verfügbar.
Pakete
Ermöglicht Ihnen die Einrichtung eines internen oder externen Feeds, in dem Automatisierungspakete gehalten werden können. Standardmäßig wird ein interner Feed verwendet. Die Feeds können entweder durch Definieren von einfachen Authentifizierungsanmeldeinformationen oder mithilfe eines API-Schlüssels gesichert werden.
| Field | Description |
|---|---|
| Internal | 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. |
| External | Must 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 URL | Only available if External is selected. The address where the NuGet feed is located. |
| Secure Deployment | Ensures that your automation packages are downloaded through a secure NuGet feed. |
| API Key | The key used to secure your feed against write operations such as delete or upload. |
| Authentication | Only 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. |
Bibliotheken
Ermöglicht Ihnen die Konfiguration des Feeds, der bei der Arbeit mit Bibliothekspaketen verwendet werden soll. Bibliotheken können über Studio veröffentlicht oder manuell vom Benutzer im Orchestrator hochgeladen und im ausgewählten Feed gespeichert werden.
| Field | Description |
|---|---|
| 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. |
| Internal | Not 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. |
| External | Not 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 Deployment | Not applicable if Only host feed is selected. Ensures that your automation packages are downloaded through a secure NuGet feed. |
| Deployment URL | Not applicable if Only host feed is selected and only available if External is selected. The address where the NuGet feed is located. |
| API Key | Not 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. |
Voraussetzungen für die Verwendung eines externen Feed Through Proxy
Wenn Sie mit einem externen Feed arbeiten möchten, während Sie unter Windows einen Proxyserver konfiguriert haben, müssen folgende Grundvoraussetzungen erfüllt sein:
- Set the Load User Profile option for the Orchestrator application pool (Internet Information Services > Application Pools) to
True.
- Fügen Sie die Proxyeinstellungen, die Sie für die Datei
NuGet.configverwendet haben und mit dem Anwendungspoolidentitätskonto verbunden sind (C:\Users\[YourAppPoolIdentityAccountName]\AppData\Roaming\NuGet\NuGet.Config), hinzu:
<config>
<add key="http_proxy" value="http://ipaddress:port" />
</config>
Hinweis
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.
Registerkarte „Sicherheit“
Roboter
| Field | Description |
|---|---|
| Run Disconnected Hours | Specify 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. |
Skalierbarkeits-Registerkarte
Geben Sie an, ob der Robot-Dienst die SignalR-Kanäle des Orchestrators abonnieren soll, und konfigurieren Sie die Transportprotokolle, die für Sie am besten sind. Diese Einstellungen werden beim Aktualisieren beibehalten.
SignalR (Roboter)
| Field | Description |
|---|---|
| Enabled | This 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. |
| WebSocket | When 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 Polling | When 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. |
Registerkarte „Arbeitsfreie Tage“
Funktionalität auf Mandantenebene.
Definieren Sie eine Liste von arbeitsfreien Tagen pro Mandant, an denen Sie die Ausführung von Triggern einschränken können. Dies bedeutet, dass Ihre langfristigen Zeitpläne an öffentlichen Feiertagen, Wochenenden oder anderen Tagen, an denen keine normalen Geschäftsaktivitäten stattfinden, so konfiguriert werden können, dass sie nicht auslösen. Nach den angegebenen arbeitsfreien Tagen löst der Zeitplan wieder normal aus.
Um diese Einschränkungen auf Ihre Trigger anzuwenden, müssen Sie beim Konfigurieren von Triggern den Kalender für arbeitsfreie Tage auswählen. Alle Änderungen, die Sie auf der Registerkarte Arbeitsfreie Tage vornehmen, wirken sich auf alle Trigger aus, die diesen Kalender verwenden.
Hinweis:
Einschränkungen für arbeitsfreie Tage sind bei Triggern deaktiviert, deren Zeitzone von der auf Mandantenebene festgelegten abweicht (Einstellungen > Allgemein). Ein Mandant, der keine ausdrücklich definierte Zeitzone hat, übernimmt diese vom Host.
For more details on how to manage non-working days, click here.
Vor ungefähr 24 Stunden aktualisiert