- Getting started
- For administrators
- RPA workflow projects
- Creating an RPA workflow from an idea
- Creating a project
- How to start an RPA workflow
- Managing project files and folders
- Connecting RPA workflows to your accounts
- Configuring activities
- Managing the activities in a project
- Passing values between activities
- Iterating through items
- Managing the data in a project
- Configuring a project to use your data
- Using file and folder resources
- Local setup for RPA workflow and app projects
- App projects
- Agentic processes
- Agents
- Solutions
- API workflows
- Tests
Studio Web user guide
The Publish button in the Studio Web toolbar gives you two options:
- Publish — packages the solution and publishes it to a feed without creating a deployment. Use this when you want to deploy the package later from the Manage tab or from Orchestrator.
- Deploy — packages the solution and creates or upgrades a deployment in one guided flow.
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 Publish button is unavailable when the solution contains errors.
To deploy to a shared workspace, you need the permissions required to create solution folders and deployments in your tenant.
Publish a solution to a feed
Use this procedure when you want to package the solution without creating a deployment.
-
In Studio Web, open the solution in the Build view.
-
Select the dropdown arrow on the Publish button, then select Publish — Package to a feed.
The publish panel opens. The WHAT WILL HAPPEN sidebar shows the steps: Setup and Publish package.
-
In the Release notes field, optionally enter a description for this version.
-
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.
-
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.
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.
Deploy a solution
Use this procedure to package and deploy a solution in one flow.
-
In Studio Web, open the solution in the Build view.
-
Select the dropdown arrow on the Publish button, then select Deploy — Publish package & create deployment.
The deployment panel opens. The WHAT WILL HAPPEN sidebar shows the steps for your specific scenario.
-
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:
Field Description Version The published version to deploy. Pre-filled with the latest available. Includes publish date and release notes hint. Deployment name Required. Pre-filled with the solution name. Location The Orchestrator folder where the solution folder will be created. Solution folder name Required. Pre-filled with the solution name. Editable if you want a custom folder name. Activate immediately When enabled, triggers are activated as soon as the deployment completes. On by default. Set up runtime When 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:
Field Description Release notes Optional description of the changes in this version. Version Required. Auto-incremented from the last published version. Editable. Includes a Last published version hint. Deployment The existing deployment to upgrade. Pre-selected. -
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.
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.
-
In Studio Web, select Manage in the toolbar to open the Manage view.
-
In the Deployments tab, select the deployment you want to activate.
The deployment detail panel opens on the right.
-
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.