Question
Evonsys
IN
Last activity: 25 Oct 2021 6:29 EDT
Ruleset changed Automatically when the Bot Started
When we start the Bot using scheduler , the ruleset changed to some FW rule set instead of original rule set .
it is getting issue like the specific bot not present under WG if RS changed . .
Robot manager 8.4.2 on Pega platform 8.4.1 & RR 19.1.51 .
Any solution ? Please Suggest .
Pegasystems Inc.
GB
Could you provide more details on which ruleset it is changing and the configuration?
Are you using the RPA service? What is the configuration in the Registration Decision Tables and Settings?
Evonsys
IN
@Angel Hermira we are having 4 applications . 1 2 3 4 .
if we start the bot in 3rd application after starting it get changed to 2nd application RS / sometimes it get register under some authentication RS , it is not register under 3rd application RS .
so when we go to robot manager > robots , we not able to see the bot that is running .
so for that when we check on org > operator ID records it present under some other RS , so we are again changing that manually to correct RS , and then bot is shown in robot manager .
yes we are using RPA Service . pyGetAccessGroupForRobotByWorkGroup is the Decision table we use . is there any way to avoid the automatic changing of RS to particular BOT operator ID . please feel free to ask if you want further details .
Pegasystems Inc.
GB
Are you using the same Registration operator in the RPA Service for all the 4 applications?
If I'm understanding it correctly. You switch to the different Work Groups using the Schedule. Each Work Group is mapped to a different Access Group and these are of different Applications. As this:
WG1-AG1-App1
WG2-AG2-App2
WG3-AG3-App3
WG4-AG4-App4
Could you confirm?
Are all 4 applications completely independent or built as an enterprise structure?
Evonsys
IN
@Angel Hermira Yes , using same Registration operator in the RPA Service config for all the 4 applications .
Each Work group is mapped to different Access Group in Decision Table . It is Like
WG1 -AG1
WG2-AG2
WG3-AG3
WG4-AG4 .
All these 4 applications are built as an Enterprise Structure .
Pegasystems Inc.
GB
@GopalakrishnanIyyavu , each AG is for a different application. Did you review this article https://community.pega.com/knowledgebase/articles/pega-robot-manager/861/understanding-basic-authentication-pega-robot-manager-users? it explains how the operator used for the robot is created/updated dynamically based on the settings. In your case if I understood it correctly. Every time it starts into a different application with a different set of ruleset.
Could you elaborate on your use case beyond the change in ruleset?. What is the issue?, What is the configuration you have in place for each application?