Connect-Robot-UiPath Deployment Strategy
We have built Pega-UiPath integration using PegaOpenRobotics 8.6 on top of PegaPlatform 8.8. Since our UiPath is hosted on cloud and Pega is on-prem and the fact we cannot allow access to on-Prem Pega platform over the internet, we are not able to use the webhooks to make a call to PegaOpenRobotics REST service Process to create Connect-Robot-UiPath instances.
Alternatively, we are calling the above API manually to create these instnaces. We have been told that whenever a process in UiPath is migrated from DEV to a higher environment (like SIT/PROD) it has a new Release key. As far as we know Connect-Robot-UiPath instances have a unique release key too.
Wondering what should be the strategy to move these instances to higher environment -Are we supposed to move these instances along with the product jar or these instances are auto-created when UiPath processes are migrated to SIT/PROD?
Pegasystems Inc.
GB
@VipinK17 I will try to find an SME for you.
@ThomasSasnett is this a question you could answer?
Pegasystems Inc.
IN
Hi, Thanks for reaching out. You can consider adding a production ruleset to your application and creating the UiPath processes on your production instance, in the same way as you did on the development server. Since there is a change in the release key, it is required to create a new process. Migrating the older processes will not identify the processes correctly. Usually, the process creation is automatic via webhooks, but as it does not work in your case, you may have to do it manually.
Thanks,
Ayush Mehrotra