Import a package version attachment in RPA Hub

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read

    • Import package version attachments automatically instead of manually uploading a package version attachment, by selecting the Import Attachment button on a package version.

    Before you begin

    Perform the following tasks before you import a package version attachment:
    • 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.
    • Ensure that there is no valid attachment associated to the package version​.
    • Verify that the life-cycle stage of the package version isn’t set to Retired.
    • Create an active connection in the RPA Automation Package connection and credential alias. Ensure to provide the lower (non-production) environment in the Connection URL field. For more information, see Create an HTTP(s) connection.

    Role required: sn_rpa_fdn.rpa_release_manager or sn_rpa_fdn.rpa_admin

    About this task

    The maximum package size is determined by the com.glide.attachment.max_size system property. For more information about this system property, Maximum allowed attachment size.

    Perform this task if you are automatically migrating the package attachment (automation zip file) from a lower (non-production) to a higher (production) environment.

    Another way to import package version attachments automatically is via triggering the Import Package Version Attachment Subflow in Workflow Studio. For more information, see Workflow Studio actions and subflow in RPA Hub.

    Procedure

    1. Navigate to All > Robotic Process Automation > RPA Hub Workspace.
    2. Select the list icon (List icon.).
    3. On the Lists tab, under Build, select Packages.
    4. Open a package whose package version you want to import.
    5. On the Package Versions tab, select a version that you want to import.
    6. Select Import Attachment.
    7. In the Confirmation dialog box, select Import Attachment.

    Result

    After the attachment is uploaded successfully or if an error occurs while uploading the attachment, an email notification is sent to the user who performs this import attachment action.

    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.