Question
Anthem
US
Last activity: 26 Jul 2017 13:20 EDT
RPA Robots
Hi,
I am developing three different RPA robots which has to run independently. I have WB and Robo will open WO and check the status. Based on the status, it will trigger the one of the automations. The question is , Each Robot has to be developed on each Solution??? . If the same Solution can be used, how to invoke the respective Robo based on the WO Status.
Pegasystems Inc.
US
For clarification, can you explain what the acronyms mean for WB and WO. Workbasket and .. WO? Others may also be confused when they look here. Generally speaking... only one solution needs to be developed - a solution can contain multiple projects or automations to handle different scenarios. After developing the solution, you would distribute the solution to each robot which would run independently on a machine.
"If the same Solution can be used, how to invoke the respective Robo based on the WO Status."
As you would grab work from the workbasket, you might have the robot observe the case and follow a specific set of actions in response. The robot would take in work from the workbasket and complete the tasks based on your automations. You, as the developer, are responsible for designing the solution to invoke specific code paths based on the input.
Anthem
US
Hello Vegam,
Thanks for the reply.
"If the same Solution can be used, how to invoke the respective Robo based on the WO Status."
"As you would grab work from the workbasket, you might have the robot observe the case and follow a specific set of actions in response. The robot would take in work from the workbasket and complete the tasks based on your automations. You, as the developer, are responsible for designing the solution to invoke specific code paths based on the input."
Let me give more information here.
1. RPA Robot 1 => Login to Pega, Read the case and status, Login Another Application ABC and execute other steps. This functionality will be repeated for all Work objects in WB
2. RPA Robot 2=> Login to Pega, Read the case and status, Login Another Application DEF and execute other steps. This functionality will be repeated for all Work objects in WB
Hello Vegam,
Thanks for the reply.
"If the same Solution can be used, how to invoke the respective Robo based on the WO Status."
"As you would grab work from the workbasket, you might have the robot observe the case and follow a specific set of actions in response. The robot would take in work from the workbasket and complete the tasks based on your automations. You, as the developer, are responsible for designing the solution to invoke specific code paths based on the input."
Let me give more information here.
1. RPA Robot 1 => Login to Pega, Read the case and status, Login Another Application ABC and execute other steps. This functionality will be repeated for all Work objects in WB
2. RPA Robot 2=> Login to Pega, Read the case and status, Login Another Application DEF and execute other steps. This functionality will be repeated for all Work objects in WB
3. RPA Robot 3 => Login to Pega, Read the case and status, Login Another Application XYZ and execute other steps. This functionality will be repeated for all Work objects in WB
Here, if One Solution to be developed, how will pass the parameter to identify respective ROBOT.
Pegasystems Inc.
US
For this example... you would have three projects (1,2,3) in your solution. Project 1 would contain an Adapter for Application ABC and associated automations that execute based on if Pega work identifies it is for ABC. Project 2 for Adapter DEF and automations to handle this application. And Project 3 for Adapter XYZ ... same way. This is how I imagine it...
Project 0?
Autx_GetWork
Autx_EvaluateWork
--> if (caseName == "NameChange") --> Start Adapter ABC --> Autx_Login_ABC
--> if (caseName == "AddressChange") --> Start Adapter DEF --> Autx_Login_DEF
--> if (caseName == "EmailChange") --> Start Adapter XYZ --> Autx_Login_XYZ
Project 1
Web Adapter ABC
Autx_Login_ABC
Project 2
Windows Adapter DEF
Autx_Login_DEF
Project 3
Windows Adapter XYZ
Autx_Login_XYZ