Document that describes how Pega Robotics v8 gets deployed for RPA
We're facing number of issues attempting to deploy RPA bots. We're developing with v8.0.1018 runtime. My installer is looking for technical documentation on how to correctly deploy an RPA bot by hand (as we cannot use the OMC). Items such as privileges (ex: run as administrator), file locations, and recommended machine settings (ex: disable screen savers, auto login, etc..) are being asked for.
I can take a guess, but if there is a reference document that would expedite my chores :)
The set up for RPA should be designed in the same regards as if an user is attending the machine during the times the bot is operating.
The Windows operating system executes security restrictions when the machine is in a locked state, so the machine cannot be locked during the operation of the RPA bot.
Screen savers, can also disrupt the automation process if enabled.
Certain applications are not designed to be used when the system is locked and may operate differently. Pega robotics operate just like a user would and therefore require the same operating conditions that they do. If our processing does not involve user applications, or if those applications operate when the system is locked, then we will also operate fine. Many of our customers have created new security policies for Robots and provide the proper security required to maintain audited access. This is not a limitation of the Pega Software since we are an event driven solution.
Any Robotic Process Automation (RPA) must have their desktop registry adjusted to ensure that the desktop or virtual machine must never lock the screen. This will ensures that anyone who remotes into a bot, to perform maintenance once they disconnect the screen will remain unlocked and the RPA will perform as designed.
Thanks for the info Zach. We have the items accounted for that you mention. However, the challenges we're seeing seem specific to how the bot applicatoins behave in the environment that are different to a user.. Obviously, the environment the bot needs has to behave like a user. But because the bot is an application in itself, it needs drive space, read/write privileges to directories/files, and such. We're a finnacial company and have numerous process and environment controls that prevent unauthorized access. Tools like Avecto and McAfee have continuely increasing restrictions & control to windows environments. Knowing exactly how Pega robotics behaves allows us to set rules in these security tools to work correctly...
What I'm asking is for what files get installed where, what files/directories need r/w access to, what (if any) registry items are affected. Can any of this items be customized? And lastly (most interesting to me at the moment) how does running Pega Runtime or studio behave differently in "Run as Administrator" which causes some bad behaviors to disappear, and other odd effects to start.. Very strange...