Are there any noted compatibility issues with recent builds of Pega Robotics 19.1 and Robot Manager 5?
Our production base install of Pega Robotics 19.1.7 is on all of our RDA machines, and we are using sync engine to run 19.1.71. We recently pushed 19.1.100 out via sync engine.
We are currently piloting a upgrade of the base install version 19.1.100 to our RDA machines in order to get the Edge extension on all the machines. We have had several users in the pilot report issues a day or two after the installation. The runtime does not open at all. After enabling verbose logging, I can see entries indicating attempts to download the runtime config from the Robot Manager. We are still on an older version of Robot Manager that does not support that feature.
We had no issues with prior versions. Have there been any bugs reported around version 19.1.100 like this?
Sorry, but my first question is the obvious one. Why are you still using RM 5 and didn't upgrade to one of the latest? RM 5 runs on Pega 7 and it is 5 years old now.
That said, the latest runtime it is compatible with all RM versions. At startup it performs a check to understand the RM version used and then uses the legacy or latest set of endpoints. The same behaviour that you are experiencing with 19.1.70 you should be experiencing with 19.1.100.
Did you verify that 19.1.70 is not raising the same set of exceptions/errors?
Posted: 3 months ago
Posted: 1 Mar 2022 9:16 EST
Brian Johnson (BrianJ9608)
@AngelHermira - The answer is the obvious one... because of the effort it will take to upgrade the platform and RM. The old version is currently working. While the new features would be nice, at this time the value does not outweigh the effort it would take to upgrade. So, until we must upgrade, or something else changes, we will remain on the old version.
Because I have only experienced this in our pilot, I am working to replicate the issue in a controlled environment. Once I can, I will report an INC. I am glad to hear that 19.1.100 should behave the same with regards to the RM. Quite often, we have an open INC and are awaiting an upgrade for a fix to robotics. I was hoping to see if anyone here had experienced anything similar, or if someone could look to see if there is an active BUG reported and being worked around this.
Posted: 3 months ago
Posted: 2 Mar 2022 5:10 EST
Angel Hermira (AngelHermira)
Principal Product Manager, Robotics
@BrianJ9608 , My understanding is that you are using RM only to manage the packages for attended RPA. Are you aware that you could also manage the RuntimeConfig.xml for the desktops?
Are you considering the effort around the update itself or the testing associated?, Updating Platform and RM if you are only using RM shouldn't be more than few hours and given that you are already using 19.1.70 and you seem to keep the runtime up to date you wouldn't need much testing since the solutions are already tested on that runtime version which is compatible with the latest Robot Manager version.
Please, let us know if you need help and perhaps we could have a call to understand your challenges and try to help with those.