UiPath Documentation
studio
latest
false
Studio user guide

Solutions

Create and manage Solutions in Studio to group automation projects with their dependencies and deploy them across tenants as a complete end-to-end automation.

Solutions group everything needed to automate an end-to-end business process, offering you the capabilities to develop automation projects together with their dependencies and deploy them across tenants as a whole.

Solutions are cloud-level containers for modeling an end-to-end automation as a single, versioned unit. In a solution, you can create and orchestrate:

  • RPA workflows
  • API workflows
  • Agents
  • Agentic processes
  • Apps (with human-in-the-loop validations)

All these components share solution-scoped resources (assets, connections, queues, storage, etc.) that you manage centrally at the solution level. Solutions are also portable—package once and deploy across tenants and organizations with environment-specific configuration.

To learn more, refer to the Studio Web user guide. For an end-to-end view of how a solution is built, packaged, and deployed, see the solution development lifecycle.

Creating solutions in Studio​

You can create a solution directly in Studio, either empty from the Start page or alongside your first project.

Starting from the Start page​

  1. On the Studio Start page, under New Project, select Solution.
  2. In the New Solution window, enter a name and a location for the solution, or keep the pre-filled values, and select Create.
    Note:

    A name that collides with an existing folder is rejected in the dialog.

Studio creates an empty solution and opens it in the Explorer panel. To add a project, select the Add to Solution button, or open the context menu of the solution's root node — both offer the same options.

Starting from a new project​

  1. In Studio, start a new Process or Template project.
  2. In the new project configuration, enable Create new solution. Studio creates the solution and opens your project as its first member in the Explorer panel.
  3. To add more projects to the solution, select the Add to Solution button in the Explorer panel. You can create a new automation project or import an existing one.
    Note:

    You can also open the context menu for the Explorer panel to access the same options.

To continue working on a solution that was originally created in Studio Web, open it from the Workspace page in Studio Web and select Open in Studio Desktop. For more options, see Managing solutions in Studio and Studio Web.

The Explorer panel​

The Explorer panel allows you to manage the projects in your solution, as well as the project files in each project.

Inside the Explorer panel, you can:

  • Use the Add to Solution Add to Solution button to open a menu with two sections:
    • Add to solution - Add a project to your solution:
      • Create a new automation project.
      • Create an automation project from a template.
      • Create a new Maestro Flow project.
      • Import an existing automation project.
    • Add to project - Add a new item to the current project:
      • A folder or a file.
      • A workflow file: sequence, flowchart, long running workflow, or state machine.
      • A form, a coded workflow, a coded test case, or a code source file.
      • A test case or a global handler.
      Note:

      You can also access the Add to Solution window by right-clicking inside the Solution panel.

  • Use the Search Search bar to find specific projects, files, pages, actions, variables, or arguments in your solution.
  • Right-click the solution to rename it, open it in Studio Web, or, for an empty solution, add a project — the same options offered by the Add to Solution button.
  • Open the context menu of the solution and select Create Automation from Template to add a project based on a template. For more information, refer to Creating a project from a template.
  • Right-click a project to:
    • Open the project in Studio and access the context menu for projects with project-specific options.
    • Open the project in Studio Web in a new browser tab.
    • Add files and folders to the project, or open its folder with Open Project Folder. These options are available for every project type in the solution. Projects that aren't active offer only Add > Folder... and File..., while the active project offers the full project menu.
    • Remove the project from the solution.

When you open a solution in Studio, you can only make changes to RPA projects and Maestro Flow projects. Other project types included in a solution cannot be modified from Studio and require you to continue editing the solution in Studio Web (this includes app projects, agentic processes, API projects, and agents).

You can browse those other, unsupported project types in the Solution Explorer alongside RPA and Flow projects. When you open a file from one of them, a contextual banner explains the limited editing experience and provides a link to edit it in Studio Web.

Creating a project from a template​

You can add a new project based on a template to a solution, without creating the project outside the solution first.

  1. In the Explorer panel, open the context menu of the solution and select Create Automation from Template.
  2. Select a template, and then configure the new project.

Studio creates the project inside the solution folder and adds it to the solution in the Explorer panel.

Creating a Maestro Flow project​

You can add a Maestro Flow project to a solution without leaving Studio.

  1. In the Explorer panel, select the Add to Solution button.
  2. Select Create Flow Project.
  3. Enter a name for the project and select Create new.

Studio scaffolds the project into the solution—the same way uip maestro flow init does from the command line—and opens the flow file.

The first time you open a .flow file, Studio prompts you to install the UiPath Maestro extension. Install it to get the full visual flow canvas; without it, the file opens as plain text.

To learn how to build out the flow itself, refer to the Maestro user guide.

Managing non-RPA projects​

Right-click any unsupported project to open it in Studio Web or remove it from the solution. Changes made in Studio Web are saved to the cloud and the project opens in a new browser tab.

The experience of designing and debugging RPA projects within a solution is the same as with standalone RPA projects, except when a project calls other projects of the solution through a Run Job activity. For more information, refer to Debugging projects that call other projects.

Note:

You cannot add or import Windows - Legacy projects into a solution.

The active project​

RPA projects and Maestro Flow projects can be the active project of a solution. If the last active project can't be restored when you open a solution, Studio activates the first project in the solution that it can open, preferring RPA projects.

You can remove any project from the solution, including the active project, as long as at least one project remains in the solution. Removing a project deletes its files, so Studio asks you to confirm the removal first. When you remove the active project:

  • The open files of the project are closed without prompting you to save them.
  • Unsaved files from other projects still prompt you to save them. Canceling the prompt cancels the removal.
  • No other project is activated automatically. Select the project you want to work on next.

Running and debugging in a solution​

Debugging projects that call other projects​

When you debug a file in a solution with more than one project, and the file calls another project of the solution through a Run Job activity, Studio prepares the solution automatically before debugging starts. Studio packs the solution, publishes it to your Personal Workspace, and deploys the called projects, so that they run as Orchestrator jobs when they are invoked. You don't need to publish the called projects or sync the solution to the cloud first.

Keep in mind the following:

  • If Studio can determine that the file you debug never reaches a Run Job call, it skips this preparation, and debugging starts right away.
  • If Studio cannot determine this, for example for coded workflows or dynamic invoke targets, it prepares the solution anyway.
  • The file you debug runs locally. Breakpoints and stepping apply only to the project you debug. The called projects run remotely, and you cannot step into them.

Running and debugging Maestro flows​

You can run and debug Maestro .flow files from the Studio ribbon, the same way as other files in the solution. The Run, Debug, Stop, Continue, Step Into, Step Over, and Step Out buttons control the flow session, and the output of the flow is displayed in the Output panel.

  • Sessions that you start from the flow canvas are also controlled from the ribbon.
  • Break is not available for flows.
  • Breakpoints, stack frames, and variables are managed in the flow canvas.
  • Running and debugging flows requires the UiPath Maestro extension.

The Defined Resources panel​

The Defined Resources panel displays the resources included in your solution. The panel can be collapsed. Resources are automatically added to a solution as they are used by activities and are grouped under these categories:

  • Apps - User interfaces powered by automations that allow you to build custom business applications which connect to data.
  • Assets - Shared variables or credentials that you can use in different automation projects.
  • Business rules - Objects used to store and manage Decision Model and Notation (DMN) files.
  • Connections - Integration Service connections that help in establishing tasks between single users and external applications.
  • Context - Context Grounding indexes that give access to permissioned knowledge bases.
  • Processes - Package versions linked to a particular folder.
  • Queues - Containers that enable you to hold an unlimited number of items.
  • Storage buckets - Per-folder storage solutions leveraged in creating automation projects.
  • Task catalogs - Action containers where you can categorize your actions based on various criteria. The catalog that stores an action is set when an action is created, using action creation activities in Studio Web.
  • Dependencies - Activity categories contextually linked into a specific project.

Resources can be created, defined, or deleted both from Studio and Studio Web. To delete a resource, right-click it in the Solution Explorer and select Remove. To learn more, refer to Solution Resources in the Studio Web guide.

Activities are aware of the solution context. Inside activities that handle solution resources (for example, Add Queue Item), the resource picker widget displays all available resources (assets, queues, connections, etc.). You can also use the Open Orchestrator button to manage platform resources in Orchestrator.

Managing solutions in Studio and Studio Web​

Changes made to a solution are always synced to the cloud, allowing you to seamlessly switch between Studio and Studio Web.

After you create a solution in Studio Web, you have the option to continue working in Studio. From the Workspace page in Studio Web, open the menu on the right side of a solution and select Open in Studio Desktop. Alternatively, open the solution in Studio Web, right-click the solution name in the Solution Explorer, and select Open in Studio Desktop.

After opening a solution created in Studio Web, select the Cloud Solution label in the status bar to open a drop-down menu with options that enable you to manage the solution:

  • Open in Browser - Open the solution in Studio Web. If the solution is locked by Studio Web, an error is displayed and the solution is opened in a new tab in read-only mode.
  • Sync with Cloud - Push the changes that you made in Studio and continue building your solution in Studio Web.

You can add a solution under Git version control by selecting the Add To Source Control label in the status bar. This allows you to manage commits and branches at solution level.

Note:
  • Studio detects when a project is part of a solution. Opening a local project that is part of a solution automatically opens the entire solution context.
  • When converting a cross-platform project to the Windows compatibility, the project is converted directly, without the option to create a copy of the original project.

Working with solutions in Studio and Studio Web​

Keep in mind these differences when working with solutions in Studio and Studio Web:

  • Renaming individual projects is currently supported only in Studio Web.
  • From Studio, you can publish the whole solution, or only the active project or its test cases. For more information, refer to Publishing a solution.
  • Some project types (agentic processes, apps, API workflows, or agents) can only be opened and edited in Studio Web. You can use Studio for its powerful RPA design and debug experiences, and Studio Web to access agentic automation features.
  • Support for solutions will be added to CI/CD integrations with UiPath CLI in the future.
  • You can view Windows projects in the Solution Explorer in Studio Web, but you can edit them only when you open the solution in Studio.
  • Only one user can work on a solution at a time. We introduced a solution-level lock to prevent unsolvable conflicts (for example, when one user builds an API workflow project in Studio Web while another edits an RPA project in Studio). Without this lock, a later sync to cloud could overwrite one set of changes. This limitation will be removed once Studio Web supports local workspaces (saving the entire solution to disk), allowing standard Git flows to safely resolve conflicts.
    Tip:
    • Use Git at the solution level to version automation projects together with their configurations.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated