orchestrator

latest

false

Getting started
- Introduction
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Time-to-live Periods
- Orchestrator Outbound IP Addresses
- Notifications
Best practices
- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- Folders
- Monitoring
- Access control
- Configuring automation capabilities
  - Enabling personal automations
    - Enabling individual users to run personal automations
- Machines
- Packages
- Audit
- Credential Stores
  - Integrating credential stores
  - Managing credential stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Settings
  - Robot Security Tab
  - Scalability Tab
    - SignalR (Robots)
Cloud robots
- Automation Cloud™ Robots - VM
- Configuring VPN for cloud robots
- My notifications
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Process Data Retention Policy
Apps
- About Apps
- Publishing an App to a Tenant
- Managing Apps
- Running a Deployed App from a Folder
Triggers
- About triggers
- Managing triggers
- Managing Non-Working Days
- Using Cron Expressions
  - Triggering jobs on the last day of the month
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
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
- Storing Assets in Azure Key Vault (read only)
- Storing Assets in HashiCorp Vault (read only)
- Storing Assets in AWS Secrets Manager (read only)
Storage Buckets
- About Storage Buckets
  - CORS/CSP Configuration
- Managing Storage Buckets
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
- Testing Data Retention Policy
Resource Catalog Service
- About Resource Catalog Service
Authentication
- About Authentication
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Classic Robots
- Robots
- Environments
  - Managing Environments
- Jobs
- Triggers
- Monitoring
  - Robots
- Resources
Troubleshooting
- About Troubleshooting
- Frequently Encountered Orchestrator Errors

Orchestrator User Guide

DELIVERY:

DELIVERY:

Automation Cloud Automation Cloud Public Sector Automation Suite Standalone

Last updated Oct 30, 2024

Unattended automation

Unattended automation is a process whereby machines perform tasks on their own, without the need for human intervention. Such tasks are usually:

complex
repetitive
carried out in batches on large amounts of data

And with the help of unattended automation, they become:

fast
scalable
reiterative
immune to errors
inexpensive
able to be run around the clock

Important:

Important: Unattended automation requires elevated permissions, access levels, and credentials, which makes it best suited for highly privileged operations.

Unattended automation is performed by unattended robots, which are deployed from Orchestrator and are programmed to execute based on a certain configuration. They run in the back-end, on dedicated machines, so users never need to interrupt their work to trigger a process.

In a nutshell, these are the components that make up an unattended automation:

docs image

The components above, as well as other concepts that are essential to unattended automations, are defined below, in the Useful concepts in unattended automation section.

Necessary permissions

This option is available to you if you meet the following permission criteria:

Role permissions
1. Machines - View, Create, and Edit
2. Users - View, Create, Edit, and Delete
3. Robots - View, Create, and Edit
Organization Administrator role - this is needed in order to create an account at the organization level and assign it to the Everyone group.
At least one of these four action combinations:
1. You have permission to view and edit robot units.
2. You have permission to view robot units and edit subfolders.
3. You have permission to view subfolders and edit robot units.
4. You have permission to view and edit subfolders.

Roles

The following roles are automatically allocated:

When creating a robot account, the Allow to be Automation User tenant role is allocated.
When selecting a folder, the Automation User folder role is allocated.

On this page

Necessary permissions
Roles

Was this page helpful?

PREVIOUSOptimizing Unattended Infrastructure Using Machine Templates

NEXTAccessing the unattended robot setup

Support and Services

Get The Help You Need

Learning RPA - Automation Courses

UiPath Community Forum

Trust and Security

© 2005-2024 UiPath. All rights reserved.