Verify the HashCode of a package version in RPA Hub

Verify the HashCode of a package version in RPA Hub so that you can validate the HashCode of the manually uploaded automation zip file with the associated package version record.

Before you begin

You must do this task in the classic environment.

Ensure that you’ve completed the tasks that are related to migrating your data from a lower environment to a higher environment. For more information, see Migrating your data from a lower environment to a higher environment in RPA Hub.

Ensure that the sn_rpa_fdn.allow_manual_upload_of_automation_package system property is marked as true. If you have the admin role, you can edit this system property.

Upload an automation package. For more information, see Upload an automation package attachment in RPA Hub.

Verify that the life-cycle stage of the package version isn’t set to Retired.

Role required: sn_rpa_fdn.rpa_release_manager

About this task

A HashCode is a unique, auto-generated alphanumeric value of a published package version that is used to validate the integrity of the package version. The system verifies the HashCode of the first attachment that is uploaded on the package version record. To ensure a successful validation, upload only the correct attachment.

Another way to verify the HashCode of a package version is via triggering the Verify HashCode of a Package Version Action in Flow Designer. For more information, see RPA Hub actions and subflow.

Procedure

  1. Navigate to All > Robotic Process Automation > Build > Packages.
  2. Open a package to view the HashCode.
  3. On the Package Versions tab, select a version.
  4. In the form header, select Verify Hash Code.

What to do next

If the HashCode validation fails, remove the invalid attachment and upload the correct automation package. For more information, see Upload an automation package attachment in RPA Hub.