Solution components - Studio Web and Orchestrator

While both workflows target solution deployment (both through Studio Web and Orchestrator), not all solution components have equal support in Studio Web, while some components are only supported via Orchestrator.

For each major product component, the tables below highlight what components are supported in each workflow:

Remarque :

Studio Web also supports additional solution resources (such as business rules, dependencies, and task catalogs) that are automatically packaged with automation projects but are not deployed as standalone solution components. For more information on those resources, see Studio Web - Designing solutions.

UiPath platform resources that can be packaged, transported and deployed as a solution

Component (product)	When designing the solution in Studio Web (recommended)	When creating the solution package from Orchestrator
Action Center - Task Catalog	✅	✅
Apps	✅	✅
Data Service - Entities & Choicesets	✅ (only as a dependency of an already published VB App that is referenced in the Solution)	✅
Integration Service - Connexions	✅	✅
Integration Service - Custom connectors	❌	✅
Orchestrator - Assets (Test, Bool, Integer, Credential)	✅	✅
Orchestrator - Processes (Robotic Process Automation, Business Process, Web App, Agent, Test Automation, API)	✅	✅
Orchestrator - Files d'attente	✅	✅
Orchestrator - Storage buckets (Orchestrator, Azure, Amazon S3)	✅	✅
Orchestrator – Webhooks	❌	✅
Orchestrator - Libraries	❌	✅
Context Grounding (Indexes)	✅	✅

The table below also includes a more granular breakdown of what Orchestrator and Integration Service triggers can be used.

Triggers (Product or Type)	When designing the solution in Studio Web (recommended)	When creating the solution package from Orchestrator
Orchestrator
→ Time	✅	✅
→ Queue	✅	✅
→ API	❌	❌
→ Events	✅	❌
Integration Service
→ Events	❌	❌

Remarque :

Only one trigger per entry point is supported. Triggers are not visible in the deployment configuration in Studio Web; they become visible and configurable when deploying from Solutions in Orchestrator.