Question
Southern California Edison Company
IN
Last activity: 5 Jul 2019 5:45 EDT
Pega Robot Manager Queries
I had setup Pega Robot manager 5.1 on Pega 7.4 platform.
We were planning to use Robot manager as a means to keep track (for licensing purposes) of all the PEGA RPA bots running in the environment. I had a few questions about the features/capabilities of PRM :
1. We use an operator id to register a Virtual Machine to Robot Manager. On registration we are able to capture the Machine Name. But can we collect the details of the operator id which is used to register the VM(for access management/audit purposes) ?
2. On unexpected shutdown of Runtime, we see that the Robot moves to 'Poor' health. Once in Poor health, we are unable to re-register the robot until we manually delete the operatorID. We cannot enable the 'RemoveStaleBot' option since we are also using Robot Manager to keep track of all the Bots(both running and inactive) in Production. Is there a way to automatically move a robot in poor health to inactive status?
3. Can we restrict roles/accesses more granularly, for ex: to restrict an operator access to modify only a specific set of packages or robots related to a particular workgroup.
I had setup Pega Robot manager 5.1 on Pega 7.4 platform.
We were planning to use Robot manager as a means to keep track (for licensing purposes) of all the PEGA RPA bots running in the environment. I had a few questions about the features/capabilities of PRM :
1. We use an operator id to register a Virtual Machine to Robot Manager. On registration we are able to capture the Machine Name. But can we collect the details of the operator id which is used to register the VM(for access management/audit purposes) ?
2. On unexpected shutdown of Runtime, we see that the Robot moves to 'Poor' health. Once in Poor health, we are unable to re-register the robot until we manually delete the operatorID. We cannot enable the 'RemoveStaleBot' option since we are also using Robot Manager to keep track of all the Bots(both running and inactive) in Production. Is there a way to automatically move a robot in poor health to inactive status?
3. Can we restrict roles/accesses more granularly, for ex: to restrict an operator access to modify only a specific set of packages or robots related to a particular workgroup.
4. When we install RPA Runtime/Studio in a machine we provide the RobotManager url and other details, but these are getting saved to the user AppData folder(RuntimeConfig.xml and StudioConfig.xml). Is there a way to ensure that these details go to ProgramData or any other user-independent location? Also can we ensure that users are not able to edit these details on their own?
Please let me know if you need any further details on these.
Any insightful replies on these queries would be really helpful :)
Pegasystems Inc.
IN
Hello Aneesh,
Please find my answers
1)You can get the registration operator id (which is used to register the robot) from the robot operator id history tab. When you open the robot operator id and go to history tab you can get i from the last added by operator id
2)Please check if ""ProcessStaleRobot" agent is enabled. This agent will delete robot operator ids which are in bad health due to lost connectivity
3)Please go through following link
4)You can change the following property in CommonConfig.xml to CommonApplicationData as below and save runtime and studio config to ProgramData location.
<ConfigurationLocation>CommonApplicationData</ConfigurationLocation>
Regards,