Deploying a solution

This step is typically performed by an administrator.

To deploy a solution, take the following steps:

1. In the Solutions window, select the desired tenant.

2. Indicate the solution package you plan to deploy. Your options are:

   • Select one of the existing solution packages available in your tenant;

   • Create a new solution package;

   • Upload a solution package from a different tenant.

3. Deploy the desired version of the solution package using its corresponding three-dot menu.
4. In the General details screen, review and update the following details:
   • General information - Read-only. Review the package name, version, description, and author;
   • Folder selection - Indicate the folder to be used as a parent folder for the solution root;
     Important:

     The solution is not deployed in the selected folder; a new child folder is created.

   • Install as a new root folder under tenant - Use the checkbox to install as a new root folder under the tenant;
   • Solution root folder name - Optionally change the root folder name, which you previously configured in the Solutions builder.
5. Select Next to go to Overview & Configuration. Now you are prompted with the Solution explorer, which allows you to review the solution components, component properties, and files.
   Note:

   • You can filter the component properties to only show read-only, configurable, or empty fields.
   • You can link and replace existing components. For details, see Linking and replacing components.
6. You can now save your solution as a draft or validate it and continue.
7. In the Deployment screen, select Start deployment.
8. To complete the deployment, take the following steps:
   1. Add accounts and assign roles - Add user or robot accounts to the solution folder(s) and assign the required roles and permissions.
   2. Add machines - Make sure machines are assigned to the solution folder(s) that include processes.
   3. Define account-machine mappings - Define account-machine mappings if needed or use dynamic allocation.
   4. Define values for assets per robot - Define value(s) for assets per robot, if applicable. This step is not needed for assets set with global values.
9. After completing all the previous steps, select the Activate deployment button to enable triggers, if any.
10. Select Close.

Linking and replacing components

The solution package contains all components required for your solution to function in a new environment. By default, all components are created in the target environment during deployment.

However, there are situations where some of the required components are already available in the target environment, and you would prefer reusing them instead of creating a duplicate. You can do this using the Link and Replace option. This functionality is available for assets and storage buckets. When linking an existing component, the solution references it and uses it instead of creating a new component as part of the solution deployment.