Publishing the Solution

Estimated reading: 4 minutes

Publishing a solution makes a complete automation available for execution and deployment. Solutions can be published locally to This PC for development and testing or to Robility Manager for centralized deployment and management.

By default, the publish type is set to This PC in Robility Designer.

Why Publish a Solution?

Publishing makes a completed automation ready for execution outside the development environment. The publishing destination determines how the solution is used and managed.

Publishing to This PC

Publish the solution to This PC when you need to:

a. Test and validate the automation locally.
b. Troubleshoot and refine the workflow during development.
c. Quickly execute the solution in a controlled environment.

Publishing to Robility Manager

Publish the solution to Robility Manager when you need to:

a. Deploy the automation for centralized execution.
b. Manage and monitor published solutions from a central location.
c. Maintain solution versions.
d. Make the solution available for execution through the managed environment.

Note

Activities that require Robility Manager project support cannot be published locally to This PC. Solutions containing these activities must be published to Robility Manager.

Benefits of Publishing Solutions

1. Easy Sharing and Reuse: Makes automation workflows available for reuse across teams and projects, promoting collaboration and consistency.
2. Centralized Management: Provides centralized management, monitoring, and version control through Robility Manager.
3. Faster Development and Testing: Enables quick local execution and validation, making it easier to troubleshoot and refine automations.
4. Flexible Deployment: Provides the flexibility to publish locally for development and testing or to Robility Manager for centralized deployment and management.

Publish a Solution to the Cloud

Follow the steps below to publish a project to the Cloud.

1. Select Publish Option

Click the Publish icon. Make sure that Project is selected as the Publish To option in the bottom-right corner.

2. Validate the Project

A publishing pop-up opens with the steps required to publish the project.

The system automatically validates the project. Once validation is completed successfully, the process moves to the Analyze Solution stage.

3. Analyze Solution

In the Analyze Solution stage, you can choose to analyze the solution or cancel the publishing process.
a. Analyze: Click Analyze to analyze the solution. After the analysis, you can choose whether to perform a security scan.
Run Scan: Scans the workflow and proceeds to the Security Scan
Skip Scan: Skips the workflow scan and proceeds directly to the Security Scan
b. Cancel: Click Cancel to cancel the current publishing process.

4. Security Scan

In the Security Scan stage, enter the required publishing information, such as: Description, Version or Release Details.
Select the required security scan option based on your publishing requirements.

5. Publish

Click Publish to publish the project. The package is verified, and once the verification is completed successfully, the process moves to the Done state. A success message is displayed with an OK option.

Note: If you click Close without clicking OK, a confirmation message is displayed asking whether you want to continue or cancel the current publishing process.

Publishing Locally

Follow the steps below to publish a project locally.

1. Select Publish Option

Click the Publish icon. Check the bottom-right corner and make sure that This PC is selected as the Publish To option for local publishing.

2. Validate the Project

Once you click Publish, the system automatically validates the project.

After successful validation, the process moves to the Packaging stage.

3. Configure Packaging

In the Packaging screen, enter the required details:

a. Description: Enter a brief summary of the solution.
b. Version: Select the required version type: Major, Minor, or Bug.
c. Release Notes: Enter details about the changes made in the solution.
d. Destination: Verify the local directory path where the package file will be saved.

4. Publish

Click Publish to publish the project.

The package is created and the process moves to the Done state. A success message is displayed with an OK option.

Note: If you click Close without clicking OK, a confirmation message is displayed asking whether you want to continue or cancel the current publishing process.

Note: Activities that require Robility Manager support cannot be published locally. These activities must be published to the Cloud.

Skip Analyzer and Security Scan

You can disable Analyzer and Security Scan from Product Configuration if you do not want these checks to run during the workflow publishing process.

When an option is disabled, the corresponding publishing step is automatically skipped.

To run a disabled check during the publishing process, select Run Now for the required step. The workflow is analyzed or scanned, and publishing continues after the check is completed.

Publishing the Solution

Publishing to This PC

Publishing to Robility Manager

Note

Benefits of Publishing Solutions

Publish a Solution to the Cloud

Publishing Locally

Skip Analyzer and Security Scan

Publishing the Solution

CONTENTS