UiPath Documentation
studio-web
latest
false
Studio Web user guide

Publishing and deploying solutions

Deploy or publish a solution from Studio Web using the toolbar's Deploy button, which also provides a dropdown option to publish without creating a deployment.

The Deploy button in the Studio Web toolbar packages and deploys a solution in one guided flow, and is the default action. Select the dropdown arrow on the Deploy button to Publish the solution instead, which packages the solution and publishes it to a feed without creating a deployment. Use Publish when you want to deploy the package later from the Manage tab or from Orchestrator.

Both options open a panel with a WHAT WILL HAPPEN sidebar that previews the steps for your specific flow before execution begins.

Prerequisites​

  • You have a solution project open in Studio Web.
  • The solution has no unresolved errors. The Deploy button is unavailable when the solution contains errors.
Note:

To deploy to a shared workspace, you need the permissions required to create solution folders and deployments in your tenant.

Deploy a solution​

Use this procedure to package and deploy a solution in one flow.

  1. In Studio Web, open the solution in the Build view.

  2. Select Deploy at the top of the page.

    The deployment panel opens. The WHAT WILL HAPPEN sidebar shows the steps for your specific scenario.

  3. Complete the deployment form based on your scenario:

    First-time deployment — the panel title is Deploy and the sidebar shows four steps: Setup, Configure, Deploy, Activate. Fill in the following fields:

    FieldDescription
    VersionThe published version to deploy. Pre-filled with the latest available. Includes publish date and release notes hint.
    Deployment nameRequired. Pre-filled with the solution name.
    LocationThe Orchestrator folder where the solution folder will be created.
    Solution folder nameRequired. Pre-filled with the solution name. Editable if you want a custom folder name.
    Activate immediatelyWhen enabled, triggers are activated as soon as the deployment completes. On by default.
    Set up runtimeWhen enabled, provisions a serverless runtime when no default execution machine is configured at the tenant level. On by default.

    Upgrading an existing deployment — the panel title is Pack and upgrade and the sidebar shows six steps: Setup, Publish package, Configure, Deactivate solution, Deploy, Activate. Fill in the following fields:

    FieldDescription
    Release notesOptional description of the changes in this version.
    VersionRequired. Auto-incremented from the last published version. Editable. Includes a Last published version hint.
    DeploymentThe existing deployment to upgrade. Pre-selected.

  4. Select the primary button — Deploy or Pack and upgrade — to begin.

    Optionally, select the dropdown arrow on the primary button and choose Customize — Deploy package, then fine-tune settings — to review and adjust individual component settings after packaging completes.

Result: The panel runs through the steps in sequence. When all steps complete, the sidebar shows green checkmarks and the main area displays Deployment successful — Solution [name] v[version] has been deployed!

From the success screen:

  • Select Back to build to return to the Build view.
  • Select View deployments to open the Manage tab for this solution.
  • Select Go to folder to open the solution folder in Orchestrator.
  • Select Start job to immediately run the deployed automation.

A Logs panel at the bottom shows the timestamped deployment output. Select Copy to copy the full log.

Publish a solution to a feed​

Use this procedure when you want to package the solution without creating a deployment.

  1. In Studio Web, open the solution in the Build view.

  2. Select the dropdown arrow on the Deploy button, then select Publish — Package to a feed.

    The publish panel opens. The WHAT WILL HAPPEN sidebar shows the steps: Setup and Publish package.

  3. In the Release notes field, optionally enter a description for this version.

  4. In the Version field, confirm or edit the version number. The field is pre-filled with the next incremented version. A Last published version hint shows the previously published version.

  5. Select Pack.

Result: The solution package is published to the feed. It appears in the Versions tab in the Manage view and in Orchestrator under Solutions > Packages. To deploy the published package, use the New deployment button in the Manage view. For more information, see Managing deployments.

Publishing individual projects from a solution​

In addition to publishing a full solution, you can publish individual RPA workflow or App projects from within a solution. This lets you update a single project's NuGet package without republishing the entire solution.

To publish an individual project from a solution:

  1. In the solution, open the context menu for the project you want to publish.
  2. Select Publish project.
  3. Complete the publish flow. The options and behavior match those of publishing a standalone project.

Result​

The project is published as a NuGet package using its existing publish bindings.

Publishing test cases from a solution​

You can publish test cases for an RPA workflow project that is part of a solution. This option is available in both Cloud Workspace and Local Workspace solutions.

To publish test cases from a solution:

  1. In the solution, open the context menu for the RPA workflow project that contains the test cases.
  2. Select Publish Test Cases.
Note:

The Publish Test Cases option is available only for RPA workflow projects that contain test cases.

Result​

The test cases are published as a NuGet package. The behavior matches publishing test cases in Studio Desktop.

Publish history panel​

The publish history panel in a solution project lists all published versions. Selecting a version item expands it, showing icon buttons with tooltips for the following actions:

  • Preview — opens the published version in read-only mode.
  • Restore — restores the solution to this published version.
  • View — opens the published version in a new tab. Available only when the publish was successful.

If a publish failed, the expanded item shows an error message. Select Copy error text to copy the error message.

Version items are not expandable while a publish is in progress.

Activate a deployment​

Use this procedure to activate a deployment that was installed but not yet activated — for example, when Activate immediately was disabled during deployment, or when a deployment shows the Inactive (Ready to activate) status.

  1. In Studio Web, select Manage in the toolbar to open the Manage view.

  2. In the Deployments tab, select the deployment you want to activate.

    The deployment detail panel opens on the right.

  3. Select Activate deployment.

Result: The activation runs immediately. When complete, the panel shows Deployment successful — Solution [name] v[version] has been deployed! with the same post-deployment actions available: Back to build, View deployments, Go to folder, and Start job. The deployment status in the grid updates to Active.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated