Our implementation is we queue the assignment to Robotic Workbasket and from there the RPA bot will take over. Then provide a handshake once the RPA Bot process is complete. Bot reference the StartupProject for deployable. We are yet to implement Robot Manager and Package Server to manage the RPA bots. We did it in Dev so updated the configuration in the RunTimeConfig XML for PegaServerURL and PackageServer tags under Robotics. This config got copied to Prod but don't have neither Robot Manager nor Package Server setup in Prod. Is there a way to get rid of these exceptions by doing any configuration changes in the RuntimeConfig or CommonConfig XMLs until we implement Robot Manager and Package Server.
Thanks. Yes we will go ahead and move the Robot Manager to all environments. Another question, in Dev we have installed the Robot Manager for Pega 7.2.2 version(PegaRoboticAutomationConsole:01.01.01). But still not able to see the Rule-Service-Rest instance robotics.v1.register or the ServicePackage robotics. Does it need any specific Access Group/Role to be added to view it.
Which version of Pega Platform and Robot Runtime are you using? Registration service wasn't introduced until RM4 before then it was using the api/v1/case endpoint to register the operator. If you are using a new runtime version. The runtime will attempt to use the latest endpoint and if not found will revert to the old one. That is probably why you're seeing the exception.
You're using something that it is 3+ years old with something that it is few months old. The solution works but you'll see the exception in the logs which you can ignore. The option to remove the exception would be to use a Runtime which is as old as the Platform but I wouldn't recommend that.
Is it not possible to upgrade the Platform version? at least to 7.3 or 7.4? That way you could run RM 4 or even RM6 which includes remote scheduling control for RPAs.