Study guide
14.3 Solutions Management: Packaging and Deploying Automations with Their Resources
UiPath Automation Developer Professional UiPath-ADPv1
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Blueprint Map
1.1 About the UiPath-ADPv1 Exam: Format, Fees & Policies 1.2 The Exam Topics Mapped to This Guide & a Study Plan
2 Chapter 2: REFramework Architecture & State Dynamics
2.1 State Machine Architecture & The Four Core States 2.2 Configuration Management: Settings, Constants, and Assets 2.3 Transaction Types & The Dispatcher vs. Performer Architecture 2.4 Adapting REFramework: Tabular Data, Collections & Linear Processes
3 Chapter 3: REFramework Exception Handling & Recovery
3.1 BusinessRuleException vs. System.Exception Handling Patterns 3.2 Retry Mechanisms: Queue Retries vs. REFramework MaxRetryNumber 3.3 Consecutive System Exceptions & Graceful Process Termination
4 Chapter 4: State Machines, Custom Log Fields & REFramework Testing
4.1 Building State Machine Projects in Studio 4.2 Logging Levels, Robot Logs & Custom Log Fields in REFramework 4.3 Testing a REFramework Project With and Without Orchestrator Queues
5 Chapter 5: LINQ Queries & DataTable Operations
5.1 LINQ Essentials for Collections & Filtering 5.2 Advanced DataTable Querying with LINQ 5.3 In-Memory DataTable Transformations & Column Operations
6 Chapter 6: Regex, DateTime, JSON & Invoke Activities
6.1 Regular Expressions & Text Parsing for Automation 6.2 DateTime Formatting, Timezone Conversions & TimeSpan Calculations 6.3 JSON Parsing, JSONPath & Serialization with Newtonsoft.Json 6.4 Invoke Method & Invoke Code Activities 6.5 Data Referencing in Invokes: DataTable, List & Dictionary Arguments
7 Chapter 7: Modern UI Automation & Unified Targeting
7.1 Modern Design Experience & The Unified Target Concept 7.2 Anchors, Relative Elements & UI Automation Activities 7.3 Dynamic Selectors, Variables & Wildcards in Selectors
8 Chapter 8: Object Repository, Computer Vision & Remote Runtime
8.1 Object Repository & UI Descriptor Libraries 8.2 AI Computer Vision for Unattended & Remote Interfaces 8.3 Automation in Virtual Environments & UiPath Remote Runtime
9 Chapter 9: Advanced UI Automation: Browser Modes, Agentic UI & macOS
9.1 Browser Automation with the WebDriver Protocol 9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent 9.3 macOS Automation: Native Apps, Office Apps & AppleScript
10 Chapter 10: Advanced Control Flow & Exception Architecture
10.1 Flowcharts, Sequences & Parallel Control Flow Patterns 10.2 Global Exception Handler Architecture & ErrorAction Directives 10.3 TryCatch, Retry Scope & Custom Exception Architectures
11 Chapter 11: Orchestrator Queues & Transaction Management
11.1 Queue Architecture, SpecificContent & Transaction Lifecycles 11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling 11.3 Bulk Operations, Transaction Status Updates & Queue Triggers
12 Chapter 12: Orchestrator Tenant & Folder Entities
12.1 Asset Types, Per-Robot Assets & External Credential Stores 12.2 Modern Folder Hierarchy, User/Robot Assignment & Permissions 12.3 Storage Buckets, Webhooks & Environment Promotion 12.4 Orchestrator Tags: Labels, Properties & Governance
13 Chapter 13: Unattended Execution, API Triggers & Cloud Robots
13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes 13.2 API Triggers: Starting Jobs from External Systems over HTTP 13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options
14 Chapter 14: Monitoring, Recording & Solutions Management
14.1 Orchestrator Monitoring, Trigger Alerts & Job Health 14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs 14.3 Solutions Management: Packaging and Deploying Automations with Their Resources
15 Chapter 15: Debugging, Remote Debugging & Profiling
15.1 Studio Debugging Tools: Breakpoints, Panels & Execution Control 15.2 Remote Debugging: Remote Machine and Unattended Robot Connections 15.3 Profile Execution: Finding Performance Bottlenecks in Studio
16 Chapter 16: RPA Testing & Test Suite
16.1 UiPath Test Suite Overview, Test Cases & Given-When-Then Structure 16.2 Data-Driven Testing, Test Verification Activities & Mock Activities 16.3 CI/CD Pipelines with uipcli & Test Manager Traceability
17 Chapter 17: Long-Running Workflows, Action Center & Apps
17.1 Long-Running Workflows: Persistence, Suspend and Resume 17.2 Action Center & Human-in-the-Loop Orchestration 17.3 UiPath Apps: Action Apps, Automations & Integration Service
18 Chapter 18: Trigger-Based Attended Automation & Callouts
18.1 Trigger-Based Attended Automation: Forms, Triggers & Global Variables 18.2 Running Local Triggers & the Event Inspection Tool 18.3 Callouts & Forms for Attended Guidance
19 Chapter 19: UiPath Assistant & Robot Sessions
19.1 UiPath Assistant: Automations, Reminders, Widgets & Configuration 19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop
20 Chapter 20: Autopilot for Developers & Autopilot for Everyone
20.1 Autopilot for Developers: AI Assistance in Studio and Studio Web 20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI
21 Chapter 21: API Automation & Integration Service
21.1 Integration Service: Connectors, Connections & Connector Activities 21.2 API Workflows in Studio Web 21.3 HTTP Requests: Web APIs, the Orchestrator API & Connector Requests 21.4 Connector Builder: Custom Integration Service Connectors 21.5 Integration Service Event Triggers: Connected and Disconnected 21.6 GenAI Activities: Generative AI Inside Workflows
22 Chapter 22: Data Service, Context Grounding & Coded Workflows
22.1 Data Fabric (Data Service) Entities: Modeling Business Data 22.2 Data Fabric Activities and the Platform Connector 22.3 Context Grounding: Retrieval-Augmented Generation with Company Data 22.4 Coded Automations: Structure, Arguments & Invoking Workflows 22.5 Coded Automation Services: Orchestrator, UI Automation, Microsoft 365 & Custom Services
23 Chapter 23: Integrated Scenario Practice
23.1 Integrated Scenario Practice: Designing an End-to-End Solution
14.3 Solutions Management: Packaging and Deploying Automations with Their Resources
Key Takeaways Explain This Topic AI
Solutions bundle projects with their Orchestrator resources, such as queues, assets, storage buckets, and triggers.
Solutions are designed in Studio Web and deployed from the Orchestrator Solutions page (Deployments, Packages, Projects).
Deployment asks for the package, version, name, location (Shared by default), solution folder name, activation, and runtime (Default Serverless offered).
Statuses are In progress, Successful, Failed (rolled back), and Failed Rollback.
Resources can be linked to existing ones, and Pipelines activities can automate uploading, deploying, and activating solutions.
Last updated: September 2026
14.3 Solutions Management: Packaging and Deploying Automations with Their Resources
Core Concept: A solution bundles an automation with the Orchestrator resources it needs, such as processes, queues, assets, storage buckets, and triggers, so the whole set can be deployed to another folder or tenant in one step. The exam description lists Solutions Management under both Orchestrator and resource management.
Why Solutions Exist
Deploying a single package leaves the rest of the setup to someone: create the queue with the right retry settings, add the assets, create the trigger, and give it all the right names. Solutions capture those resources together, which makes promotion from a development tenant to test and production repeatable.
Lifecycle
- Step Where What happens
- Design Studio Web Build a solution that contains one or more projects and the resources they use
- Publish Studio Web The solution is published as a solution package with a version
- Deploy Orchestrator > Solutions Choose the package and version and deploy it to a location
- Activate Orchestrator Make the deployed resources active, immediately or later
- Upgrade or uninstall Orchestrator Deploy a newer version over the existing deployment, or remove it
The Solutions page in Orchestrator has tabs for Deployments , Packages , and Projects . Solutions Management is an Automation Cloud capability.
Deploying a Solution Package
The deployment form asks for:
- Field Meaning
- Package and Version Which solution package and version to deploy
- Deployment name A name for this deployment
- Location The parent folder where the solution folder is created; Shared by default
- Solution folder name The folder created for the solution's resources
- Activate immediately Whether resources become active right after deployment
- Set up runtime The machine template used to run the processes; Default Serverless is offered by default
- Deployment statuses
- Status Meaning
- In progress The deployment is running
- Successful All resources were created
- Failed Something went wrong and the deployment was rolled back
- Failed Rollback The rollback itself failed and needs attention
- Configuration and Existing Resources
A deployment does not have to create everything from scratch:
Before deploying, review the configuration of the resources, such as asset values and queue settings for the target environment.
A solution resource can be linked to an existing resource in the target, such as an asset, storage bucket, webhook, or queue that already exists, instead of creating a duplicate.
Environment-specific values belong in the deployment configuration, not in the workflow.
Permissions
Solution deployments and packages have their own tenant permissions (Solution deployments and Solution packages: View, Edit, Create, Delete), which the Orchestrator Administrator role includes. Orchestrator also has the default roles Solutions Administrator and Solutions Contributor for teams that manage solutions without full administration rights.
Solutions Versus Deploying Packages Only
- Aspect Package only Solution
- Contains Workflows and dependencies Projects plus Orchestrator resources and their configuration
- Queues, assets, buckets, triggers Created manually in each environment Created or linked by the deployment
- Rollback on failure Manual clean-up Failed deployments roll back automatically
- Designed in Studio or Studio Web Studio Web
Best for A single process with few resources A multi-process automation with many resources, promoted across environments
Automating Deployments
Automation Ops Pipelines include solution activities such as Upload Solution Package , Deploy Solution , and Activate Solution Deployment . This lets teams add solutions to CI/CD, with approval steps before production.
Worked Example
A team builds an invoice solution in Studio Web with three projects: a dispatcher, a performer, and a reporting process. It uses one queue, two assets, one storage bucket, and a queue trigger.
Publish the solution as version 1.0.0.
In the test tenant, open Orchestrator > Solutions > Packages and deploy 1.0.0 to Shared with the solution folder name Invoices , the runtime Default Serverless for the background processes, and Activate immediately turned off.
Review the configuration: set the test API URL asset, and link the storage bucket to the test tenant's existing InvoiceFiles bucket.
Deploy. The status shows In progress , then Successful .
Activate the deployment and run a test batch.
Promote the same package version to production with production values.
If step 4 had failed, for example because a resource name already existed and was not linked, the deployment would roll back and show Failed .
Good Practices
Keep environment-specific values, such as URLs and credentials, in the deployment configuration or in linked assets, never hard-coded in the projects.
Deploy with Activate immediately turned off in production, check the configuration, and then activate.
Use a clear deployment name and version so the Deployments tab shows what runs where.
Common Traps
Solutions are designed in Studio Web ; deployment happens in Orchestrator's Solutions page.
The default location is the Shared folder, with a new solution folder created under it.
A failed deployment rolls back; Failed Rollback needs manual attention.
Existing resources can be linked instead of duplicated.