- Release notes
- 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
- App projects
- Agentic processes
- Agents
- Solutions - Preview
- Creating solutions
- Managing solutions
- Debugging solutions
- Publishing and deploying solutions
- Known limitations
Studio Web User Guide
Publishing and deploying solutions
Publishing a solution creates a solution package.
Before solutions in a unified developer experience, each project was individually published as a NuGet package. While NuGet packages continue to be the way to pack individual automations, the entire solution is packed in a ZIP file.
The solution package contains all the deployment configurations, as well as the corresponding NuGet packages pertaining to each automation project. The solution package is transferable across tenants and organizations.
- Select the Publish button at the top of the designer.
- In the Publish solution window, enter a name and a description for your solution, and select a version.
- Under Location, choose where to publish your solution: Orchestrator Tenant or Personal Workspace.
- Select Publish.
Solutions are published differently depending on the location you have selected.
When you publish to an Orchestrator Tenant, a validation message appears in your solution designer once the solution package is created. A notification also appears in the Notifications panel.
To check the published solution package, select the Check package link in the validation message. You are then directed to the Tenant > Solutions > Packages > Package Versions page in Orchestrator.
For the developed automations to become executable, the solution package needs to be deployed.
When you publish to your Personal Workspace, a validation message appears in your solution designer once the solution package is created. For convenience, publishing a solution to your Personal Workspace automatically performs a deployment, to bring the automation to an executable state.
To check the published and deployed solution package, select the Check Automation link in the validation message. You are then directed to the My Workspace > Solutions > Deployments > Deployment Summary page in Orchestrator.
Solutions are deployed as a whole. To minimize the manual tasks performed during deployment, reduce potential errors, and facilitate the development process, you can set the deployment configuration of a solution at design time.
This can be done from the Deployment configuration panel, where everything that will be deployed is listed along its respective configuration.
To learn more about deploying a solution published to an Orchestrator Tenant, refer to Deploying a solution in the Solutions Management user guide.
Solutions published to a Personal Workspace are automatically deployed during publishing.
- Navigating to the toolbar above the Studio Web designer.
- Selecting the
arrow next to the test environment.
- Selecting Deploy solution for testing from the drop-down menu.
