multiple RPAs refer to one RobotQueue
We are considering developing a system combining PegaPlatform and PegaRPA.
【background】
It uses the RobotQueue shape on PegaPlatform's case, and uses the flow to operate RPA installed in another environment.
The time taken to process one RPA is relatively long, and in order to prevent RobotQueue from staying, prepare multiple environments in which the same robot is installed.
I want to make sure that Queue does not stay.
【Question matters】
-If multiple RPAs refer to one RobotQueue, is it likely that an error will occur when trying to obtain assignments from the Queue at the same time?
Example) When the same RPA is introduced to terminal A and terminal B, and the flow transitions to RobotQueue,
Terminal A acquires an assignment, and terminal B can not acquire an assignment, resulting in an error and stacking.
・ If the above error occurs, it is best practice not to occur
【Application configuration】
◆ Pega Platform side (Pega Platform: 7.2.2)
Place a Robot Queue shape on the case, and make the following settings.
・ Route to queue: Robot 1WB
・ Run robotic automation: Robot 1
◆ PegaRPA side (Pega Robotic Automation)
The same robot is placed on multiple terminals, and both refer to the same work basket.
Terminal A: The robot 1 is arranged. Refer to robot 1WB on the Pega Platform side.
Terminal B: The robot 1 is arranged. Refer to robot 1WB on the Pega Platform side.
We are considering developing a system combining PegaPlatform and PegaRPA.
【background】
It uses the RobotQueue shape on PegaPlatform's case, and uses the flow to operate RPA installed in another environment.
The time taken to process one RPA is relatively long, and in order to prevent RobotQueue from staying, prepare multiple environments in which the same robot is installed.
I want to make sure that Queue does not stay.
【Question matters】
-If multiple RPAs refer to one RobotQueue, is it likely that an error will occur when trying to obtain assignments from the Queue at the same time?
Example) When the same RPA is introduced to terminal A and terminal B, and the flow transitions to RobotQueue,
Terminal A acquires an assignment, and terminal B can not acquire an assignment, resulting in an error and stacking.
・ If the above error occurs, it is best practice not to occur
【Application configuration】
◆ Pega Platform side (Pega Platform: 7.2.2)
Place a Robot Queue shape on the case, and make the following settings.
・ Route to queue: Robot 1WB
・ Run robotic automation: Robot 1
◆ PegaRPA side (Pega Robotic Automation)
The same robot is placed on multiple terminals, and both refer to the same work basket.
Terminal A: The robot 1 is arranged. Refer to robot 1WB on the Pega Platform side.
Terminal B: The robot 1 is arranged. Refer to robot 1WB on the Pega Platform side.
***Moderator Edit-Vidyaranjan: Updated SR details***
Pegasystems Inc.
US
There seems to be only one question early on in your paragraph, so that is what I am focusing on answering. Forgive me if I missed something else. A work queue is what each bot will work from. They will request one piece of work from the work queue at a time. That work will be assigned by Robot Manager to a single bot. It is not possible for multiple bots to acquire the same piece of work.