Posted: 4 Mar 2017 8:08 EST Last activity: 10 Mar 2017 7:10 EST
Possible approach for integrating Pega with RDA invoking a long-running session
Hi. When integrating RDA with Pega, and if the automation is a long-running session taking a few minutes, what approaches can be thought?
Since the automation is executed as Flow Action's pre- or post-process, the browser might timeout while the robot is working.
Using RPA? Any other approaches can be thought?
* Based on my quick investigation with using Pega 7.2.2 and Robotics 8.0 Build 1025, even when we put SetCompletionStatus method in the middle of the RobotActivity, the response from the robot is actually held till all the steps in the relevant Automation is completed. I also tried using Interaction Framework to check if completion is notified to Pega before completing the execution of IF, but the situation was the same, i.e., it held till IF execution was completed.
A long running process really should be done with RPA. I suspect there are ways to trick the process into thinking it is done by triggering a new execution thread but is your process done enough to accurately set the completion status? If you want to try - have your Robot Activity turn on a timer and then set completion status and then end. Set the timer to quickly fire and then disable it and continue your automation. You would need to institute some flow control on the Robot Activities so that it would wait if your rogue process was still running.