Upload an automation package attachment in RPA Hub
Upload a zip file of the automation package in RPA Hub to manually migrate the package from a lower (non-production) to a higher (production) environment.
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.
Download the package version attachment from a lower instance. For more information, see Download a package version 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.
Verify that the life-cycle stage of the package version isn’t set to Retired.
Ensure that there’s no valid attachment that is associated with the package version record.
For a quick integrity check, verify that the HashCode of a package version is correct. If the validation fails, remove the incorrect attachment that you previously uploaded by selecting Manage Attachments. Then, proceed with this task to upload a correct attachment. For more information about verifying the HashCode, see Verify the HashCode of a package version in RPA Hub.
Role required: sn_rpa_fdn.rpa_release_manager
About this task
You can upload the valid attachment only one time. The Upload Attachment button to upload attachments is turned off after you upload a valid attachment.
Procedure
- Navigate to .
- Open a package that you want to upload a package version for.
- On the Package Versions tab, select a version.
- In the form header, select Upload Attachment to upload a zip file of the automation package.
- In the Confirmation dialog box, select Choose file.
What to do next
For a quick integrity check, verify the HashCode of a package version again. For more information, see Verify the HashCode of a package version in RPA Hub.