Domain issue in Promotion/Migration of RPA Assets - Support and Troubleshooting

Domain issue in Promotion/Migration of RPA Assets Issue In a non-domain separated instance, when we migrate the bot process and corresponding configuration using promotion of RPA Assets from one instance to another, we noticed a change in the value populated in the domain field type for migrated configuration records like Queue, process Parameters etc... In the source instance, it was a static string with the value 'global'. However, after migration, in the target instance, the domain field value changed to a sys_user_group reference with name as 'global'.

Symptoms After a successful migration, you will observe that the domain field value in the migrated tables now references the sys_user_group table with the name as 'global'. The tables affected by this change include:

sn_rpa_fdn_bot_process_config sn_rpa_fdn_package sn_rpa_fdn_package_version sn_rpa_fdn_m2m_package_version_skill_mapping sn_rpa_fdn_m2m_process_skill_mapping sn_rpa_fdn_schedule sn_rpa_fdn_process_parameter sn_rpa_fdn_m2m_process_param_process sn_rpa_fdn_work_queue sn_rpa_fdn_m2m_process_queue sn_rpa_fdn_attended_configuration sn_rpa_fdn_process_field_parameter sn_rpa_fdn_field_parameter_mapping Release We have thoroughly examined and validated the issues with the Xanadu version of our product. Our team has dedicated significant effort to identify and test these problems to ensure the most accurate resolution. We are pleased to announce that we will be releasing a fix for these issues in the middle of June 2025. This fix will address the concerns that have been raised and provide a more seamless experience for our users.

Resolution Kindly follow the steps below before starting the migration:

Please check the sys_user_group table for any record whose name is global . If found, delete the record.

Please follow the below steps to resolve the migration of bot configuration domain issue for non-domain separated instance:

Import the BR XML into Target instance. Target Instance -> All> system Definition> Business rules -> click on 3 dots on any column> select import XML and import. Whenever you are ready to migrate the bot processes or before migration, navigate to Target Instance -> All> Business rules -> open imported xml (i.e imported BR) > Activate it . This step ensures that the imported business rule is ready for use in the target instance. Now Migrate the required bot processes. This step involves moving the specific bot processes from the source instance to the target instance. Verify in Target instance whether all the content is migrated or not. It is essential to confirm that all the necessary tables, including bot processes, and configurations like Schedules, Process Parameters, Queues etc.., have been successfully migrated to the target instance. Verify now that the migrated bot configuration related tables is having domain field value as static string 'global'. This step ensures that the configuration parameters are set correctly for the migrated bot related tables in the target instance. If all the bot configs are migrated then de-activate the BR .

Note : Kindly ensure that all relevant steps are carefully followed both before and after the migration of RPA assets from the source to the target instance. It is important to maintain the metadata from the source instance consistently across all target instances. Additionally, please ensure that no migrated record data is deleted, even if any issues arise during or after the migration process.