- Introduction
- Managing solution projects and packages
- Manage a solution project in Orchestrator
- Manage a solution package in Orchestrator
- Navigating the package sidebar
- Managing solution deployments
- Best practices
Solutions user guide
This task is typically performed by an RPA developer.
You can create a solution via Studio Web or via the Solutions builder in Orchestrator.
Use the Solutions builder in Orchestrator to assemble a solution project based on already published artifacts. If you are building your solution from scratch, we recommend Studio Web.
Create a solution project
Create a solution in Studio Web
To start building a solution in Studio Web, refer to the steps described in Creating solutions and Designing solutions from the Studio Web user guide.
Once your solution is built, you can publish it to an Orchestrator tenant or to your Personal Workspace. To learn how to publish a solution, refer to Publishing and deploying solutions from the Studio Web guide.
Create a solution in Orchestrator
-
Select the Solutions tab at tenant level.
-
Select the Projects tab then the New project button.
-
In the Create solution project window, provide a name for the project and, optionally, a description, then select Create.
-
Once the Solutions builder is open, select the + button to start building your solution by adding components from the selected tenant.
-
In the Components panel, select the components you plan to include in your solution. Note that you can only observe the components you have access to in the source environment.

-
Select the components included in your solution to view and optionally update their properties in the Component properties panel. Note that there are two types of properties:
-
Read-only properties - Changing these properties may break the solution. The only way to change read-only properties is by going back to your development environment and making the changes. Then, come back to the Solution builder to remove the old component, then reimport it to fetch the latest info.
-
Configurable properties - If you know that different values are required in the target deployment environment, you can configure these properties to ease the deployment experience. You can also change these properties within the deployment wizard if needed.
Note:In cases where property differences across environments exist, and the correct values are uncertain during the solution packaging process, it is recommended to leave these fields blank by removing the default values. This way, it is easier to notice which fields require specific input during the deployment phase.

-
-
To generate a solution package, select the Publish button in the upper-right corner of the Solution explorer window, and provide the following details in the newly open panel:
- Solution root folder name - Mandatory. The name provided at deployment time for the solution root folder. The administrator can change it when performing a deployment.
- Package name — Mandatory.
- Package version - Mandatory.
- Description - Optional.
-
Select Publish.
-
Return to the Solutions view in Orchestrator. You should now observe your newly created packages in the Packages tab.
You can interact with the aforementioned flow at any time and return to the Projects tab to resume work on your project.
Edit a published solution project
You can edit a published project so that you can apply any of the following changes:
- Changes to the solution structure: add or remove solution components.
- Changes to the component properties.
To edit a published solution project, you can open a solution project in Studio Web, or take the following steps in Orchestrator:
-
Select the Solutions tab at tenant level.
-
Navigate to the Projects tab and locate the solution project you want to modify. Select the three-dot menu, then proceed to edit the targeted version.
The Solutions builder now opens.
-
The Solution explorer and Component properties panels are now open, allowing you to make the desired changes:
-
Changes to the solution structure: add or remove solution components.
-
Changes to the component properties.
Note:If you make changes to read-only component properties in the source environment, you must use the Sync functionality to fetch the latest data.
As a general rule, you can update any of the configurations that were also editable at initial deployment time. However, there are some properties that you cannot change if they were configured in a certain way, as is the case of the store in encrypted format for queues.
-
-
Once you are done making changes, select Publish. You have now created a new solution package version.