- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Setup Samples
- Storing Robot Credentials in CyberArk
- Setting up Attended Robots
- Setting up Unattended Robots
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Managing Folders
- Classic Folders Vs Modern Folders
- Migrating From Classic Folders to Modern Folders
- Administration of Modern Folders
- Personal Workspaces
- Managing Personal Workspaces
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Integrations
- Classic Robots
- Troubleshooting
Migrating From Classic Folders to Modern Folders
To take advantage of the features provided by modern folders, you must recompile existing workflows that are using Orchestrator activities or are making direct HTTP calls to the Orchestrator API, using UiPath.System.Activities v19.10.1 or higher. You must also reprovision all other existing entities in a modern folder structure except for:
- Robots - as they are automatically provisioned for users with access to the new modern folder; and
- Environments - as they are not used in the context of a modern folder.
To convert your current deployment, in whole or in part, to utilize modern folders, some entities must be redeployed while others must be recreated entirely.
A general overview of the migration process can be thought of as follows:
- Each previous Organization Unit, or Tenant if no OU's were used, becomes a First Level Folder. This is done automatically when you upgrade your Orchestrator instance.
- Each Environment becomes a separate subfolder or, alternatively, its own first-level Folder if you want to keep the users and processes in each segregated completely.
- The workflow of each Package must be recompiled using current activities and then republished or uploaded to Orchestrator.
- Using the newly compiled Packages, each Process must be redeployed to the Folder (or subfolder), which corresponds with its previous Environment.
- Each User must be added to the Folder(s) corresponding with the Processes they need to access.
domain\username, one in a classic folder and one in a modern folder, and the user sees and executes only the classic processes available
to them. When the classic robot is deleted, the modern robot takes over and executes the newly created and added modern versions
of those same processes, with no change in the user's experience.
domain/username as a user in a modern folder, the user will only have access to the classic robot and related processes. In order for the
attended robot to work in a modern context, the classic floating robot has to be deactivated. After the migration is successfully
tested and vetted, the classic robot can safely be deleted.
To simplify the process of migrating to modern folders, you can use the UiPath Orchestration Manager. This is a Studio project that uses the Orchestrator API to manipulate entities based on Microsoft Excel workbooks. For instructions on how to use it for migration, see the product's documentation.
