orchestrator

2021.10

false

Getting started
- Introduction
- User Options
- Logging in to Orchestrator
- Resetting Your Password
- My Profile
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Orchestrator Configuration Checklist
Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
Tenant
- About the Tenant Context
- Robots
- Folders
- Managing Access and Automation Capabilities
- Machines
- Packages
- Audit
- Credential Stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Alerts
  - Setting Up Alert Emails
- Settings
  - General Tab
  - Deployment Tab
  - Security Tab
  - Scalability Tab
  - Non-Working Days Tab
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- About Recording
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
Triggers
- About Triggers
- Managing Triggers
- Using Cron Expressions
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- Orchestrator Logs
Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
Queues
- About Queues and Transactions
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
  - Editing Transactions
  - Field Descriptions for the Transactions .csv File
- Review Requests
Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
Storage Buckets
- About Storage Buckets
  - CORS/CSP Configuration
- Managing Storage Buckets
- Moving Bucket Data Between Storage Providers
Test Suite - Orchestrator
- Test Automation
- Test Cases
  - Field Descriptions for the Test Cases Page
- Test Sets
  - Field Descriptions for the Test Sets Page
- Test Executions
  - Field Descriptions for the Test Executions Page
- Test Schedules
  - Field Descriptions for the Test Schedules Page
- Test Data Queues
Other Configurations
- Increasing the Size Limit of Package Files
- Setting up Encryption Key Per Tenant
- GZIP Compression
Integrations
- About Input and Output Arguments
  - Providing Argument Values
    - Orchestrator API
  - Example of Using Input and Output Arguments
Classic Robots
- Robots
- Environments
  - Best Practices
  - Managing Environments
- Jobs
  - Long-Running Workflows
    - Queues
    - Duration
- Triggers
  - Time Triggers
    - Queued Jobs Scenarios
  - Queue Triggers
- Monitoring
  - Robots
- Resources
Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Configuring host authentication settings
- Managing your host license
  - Allocating host licenses to organizations
- Configuring system email notifications
- Configuring other host settings
  - Customizing the Login page
  - Orchestrator host settings
    - Tenant Settings - Host Level
- Audit logs for the host portal
- Maintenance Mode
Organization administration
- About organizations
- About Licensing
  - Activating your license
- Accounts and Groups
- Registering External Applications
  - Managing External Applications
- Audit logs
Troubleshooting
- About Troubleshooting
- Cron Expressions
- Upgrade Issues
- Frequently Encountered Orchestrator Errors

OUT OF SUPPORT

Orchestrator User Guide

DELIVERY:

DELIVERY:

Automation Cloud Automation Cloud Public Sector Automation Suite Standalone

Last updated Oct 31, 2024

Security Tab

Robot

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.

On this page

Robot

Was this page helpful?

PREVIOUSDeployment Tab

NEXTScalability Tab

Support and Services

Get The Help You Need

Learning RPA - Automation Courses

UiPath Community Forum

Trust and Security

© 2005-2024 UiPath. All rights reserved.