Migrating your data from a lower environment to a higher environment in RPA Hub

As a system administrator, after you restructure the RPA Hub tables to extend the Application file (sys_metadata), you can use the update set capability to migrate your data from a lower (non-production) environment to a higher (production) environment for real-time use.

There are two ways you can migrate your data from a lower environment to a higher environment:

• Using the update set capability described in this page for migrating your data from one environment to another environment
• Using the Migrate button in RPA Hub

  In RPA Hub, you can migrate the bot process configuration and associated assets from one environment to another environment with a click of a button. After the migration is complete, you will have to create a bot process record, create credentials, make necessary changes, and then publish the bot process. For more information, see Migrating the bot process configuration in RPA Hub.

Restructured RPA Hub tables (Tokyo and earlier releases)

For more information about the restructuring of the RPA Hub tables, see Restructuring RPA Hub tables.

For more information about update sets, see Get started with update sets.

Functionality

The metadata of the automation (package, package version, schedules, and so on) is captured in the update set. System administrator then moves the update set to a higher (production) environment.

The metadata records are moved to the higher (production) environment but the package version does not contain an automation zip file.

RPA release manager manually downloads the zip file from the lower (non-production) environment and then uploads it to a higher (production environment). RPA admin can also perform this action. However, this task is restricted to classic environment.

RPA release manager automatically imports package version attachments by selecting the Import Attachment button on a package version. RPA admin can also perform this action. A flow is then triggered asynchronously and pulls the attachment from the configured connection using API. The automation zip file is attached to the package version and HashCode validation is performed automatically. An email is also sent to the user who performs the import attachment action.

To execute the orchestration of RPA Hub update sets from third-party tools, it is essential to recreate bot process on the higher environment. The Change Life Cycle Stage Status of a Bot Process action in Workflow Studio helps in ensuring the deployment and enablement of RPA Hub process is automated. For more information about this action, see Workflow Studio actions and subflow in RPA Hub.

List of steps for the migration tasks

Use this list of steps to guide you through all the tasks of the migration.

Complete all the tasks for a step before moving on to the next step.

Do the steps in the order that they’re presented.

Table 1. Checklist

Task	Environment
1. Create and select an update set as the current set.	Lower (non-production) environment
2. Create a bot process configuration record in RPA Hub.	Lower (non-production) environment
3. Adding details to your bot process in RPA Hub.	Lower (non-production) environment
4. Mark your current update set complete.	Lower (non-production) environment
5. Export to XML.	Lower (non-production) environment
6. Download a package version in RPA Hub. Perform this task, if you are manually migrating the package attachment (automation zip file) from a lower (non-production) to a higher (production) environment. You can skip step 12.	Lower (non-production) environment
7. Switch to higher instance. Retrieve an update set.	Higher (production) environment
8. Preview a remote update set.	Higher (production) environment
9. Commit an update set.	Higher (production) environment
10. Associate a bot process to a bot process configuration record.	Higher (production) environment
11. Verify the associated schedules, parameters, packages, and queues in RPA Hub.	Higher (production) environment
12. If the instance connection is established with a required lower (non-production) instance, perform this import task. To establish an instance connection, 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. Perform this task if you are automatically migrating the package attachment (automation zip file) from a lower (non-production) to a higher (production) environment. Import a package version attachment in RPA Hub. You can skip step 13 and 14.	Higher (production) environment
13. Upload an automation package attachment in RPA Hub. Perform this task in classic environment.	Higher (production) environment
14. Verify the HashCode of a package version in RPA Hub.	Higher (production) environment
15. Assign a business application to a bot process in RPA Hub.	Higher (production) environment
16. Create a credential group in RPA Hub.	Higher (production) environment
17. Assign a robot to a bot process in RPA Hub.	Higher (production) environment
18. Assign a process robot credential within a bot process in RPA Hub.	Higher (production) environment
19. Assign an attended user or group to an attended bot process.	Higher (production) environment

• Import a package version attachment in RPA Hub
  Import package version attachments automatically instead of manually uploading a package version attachment, by selecting the Import Attachment button on a package version.
• 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.