Migrating the bot process configuration in RPA Hub
Summarize
Summary of Migrating the Bot Process Configuration in RPA Hub
In RPA Hub, users can migrate bot process configurations and related assets between environments, facilitating the transition of automation from development to production. This feature supports both attended and unattended bot processes, allowing for effective testing and deployment across various environments.
Show less
Key Features
- Migration from any environment to any environment, such as from development to UAT.
- Selection of the "Ready for Migration" button to initiate migration.
- Visibility of the "Migrate" button only when no migration is in progress.
- Post-migration modifications like creating process parameters and mapping credentials in the target environment.
Key Outcomes
During migration, the following assets are transferred:
- For unattended processes: Bot process configuration, packages, package versions with attachments, process parameters, shared parameters, schedules, queues, and associated skills.
- For attended processes: All items from unattended migration plus process field parameters and attended configurations if Embedded Task Automation (ETA) is enabled.
Note that the following are not migrated:
- Robot credentials, application credentials, and credential groups.
- Sensitive values in shared or process parameters are not transferred; only default field values are migrated.
- Custom field values are not included in the migration.
For users on Tokyo and earlier releases, restructuring of RPA Hub tables is required before migration.
In RPA Hub, you can migrate the bot process configuration and associated assets for an attended or unattended bot process from one environment to another environment. With this feature, you can create an automation and test it in a lower environment and then migrate it to a higher or production environment.
Bot process migration overview
You can migrate the bot processes from any environment to any environment. For example, when a bot process is ready to be migrated from a developer’s environment to a UAT environment, an RPA developer or RPA administrator can select the Ready for Migration button on a published bot process. This action enables the Migrate button to appear. This button is only visible when the bot process migration isn’t in progress. Then, an RPA release manager or RPA administrator can initiate the migration process by selecting the Migrate button. After the bot process and associated assets are migrated, a release manager can make any necessary changes (such as creating more process parameters, shared parameters, or credential mapping), create and associate credentials, create an associated bot process record, and publish the bot process on the UAT (target) environment.
What's migrated with the bot process
- Bot process configuration
- Packages
- Package versions with attachments
- Process parameters
- Shared process parameters, if assigned to the bot process
- Schedules
- Queues
- Associated skills
In an attended bot process migration, the following records and associated assets are also migrated:
- Bot process configuration
- Packages
- Package versions with attachments
- Process parameters
- Shared process parameters, if assigned to the bot process
- Process field parameters, if Embedded Task Automation (ETA) is enabled
- Attended configurations, if ETA is enabled
- Queues
- Associated skills
What's not migrated with the bot process
The robot credentials, application credentials, and credential group that are associated with the bot process configuration aren't migrated. After the bot process configuration is migrated, the credentials must be created or updated in the target environment.
If any shared parameters or process parameters are marked as sensitive in the bot process, the sensitive values that are stored in these parameters aren't migrated and the parameter values are empty in the target environment.
Only the default field values are migrated. The custom field values aren't migrated.
Restructured RPA Hub tables (Tokyo and earlier releases)
For Tokyo and earlier releases, you must restructure the RPA Hub tables before migration. For more information, see Restructuring RPA Hub tables.