Publish an automation project to RPA Hub from RPA Desktop Design Studio.

Before you begin

Ensure that the automation is open in RPA Desktop Design Studio. For more information, see Create an automation project in RPA Desktop Design Studio and Open a local automation project in RPA Desktop Design Studio.

Ensure that the automation project file is located in a separate folder. All the files and folders in the current project file location are published to the RPA Hub.

For code signing the automation package, do the following tasks:

Verify the connection manager setup in the RPA Desktop Design Studio. For more information, see Set up RPA Desktop Design Studio.

Role required: sn_rpa_fdn.rpa_developer or sn_rpa_fdn.rpa_admin

Procedure

  1. In the RPA Desktop Design Studio, open the automation project that you want to publish.
  2. On the Design tab, select Publish. .
    Important:
    • If the Code quality check feature is enabled from your RPA Hub instance and your automation project has Code quality check issues, the Code Quality Check Results window displays an error message.

      Code quality check performed during publishing of a project.

      You can publish a package with errors, or a combination of errors and warnings only if the property sn_rpa_fdn.restrict_package_by_severity is set as No restriction in RPA Hub. For more information on this property, see Configure RPA Hub properties. These packages are highlighted with the message Automation contains one or more errors or warnings when you proceed with publishing a project.
      Figure 1. Error displayed when you're publishing a project with errors or warnings
      Error displayed when you're publishing a project with errors or warnings.

      For more information on the compliance rules that the Code quality check follows if a package is published from RPA Desktop Design Studio, see Code quality check compliance for RPA Desktop Design Studio.

    • When you enable the sn_rpa_fdn.code_signing_required system property on the instance, it impacts the existing bot processes that are associated with packages on the same instance because you had not code signed them earlier while publishing from the RPA Desktop Design Studio to the RPA Hub. As a result, the automations corresponding to these bot processes fail. To run the failed automations successfully, you must publish the package again with the code signing from the RPA Desktop Design Studio to RPA Hub.
  3. In the Publish Project dialog box, in the Publish as field, select either New Package or New Version (to existing package).
  4. In the Package name field, enter the package name.
  5. (Optional) If you want to select an existing package, select Select Package.
  6. In the Comments field, enter a detailed description or any updates for the project.
  7. (Optional) If code signing is mandated by your organization, do the following actions:
    1. In the Certificate location field, select either File or Cert Store as the location of the certificate.
    2. Select the three-dot menu (Three-dot menu.) next to the Certificate field.
    3. Select the installed code signing certificate.
      Note: You can only select a certificate that has the intended purpose as code signing. If you select a certificate with any other intended purpose, an error is displayed.
    4. Select OK.
  8. Select Publish.
  9. In the Confirmation dialog box, select OK.