Hi all,
I would like to start a discussion about one thing that I guess most of us (if not everybody) suffers from time to time. Sometimes robot execution terminates because the backend application where the robots tries to execute the process (SAP, web application...) has changed and then we need to recalibrate the robot again.
The position we have in general about this issues is just reactive, we wait until the application change, the robot crash and then we fix it but I would like to have a more proactive approach. The options I see are the next:
1) Speak with IT and other stakeholders so we are informed about future changes: In few cases is an option but, in general, simply there are too many changes to use this option broadly
2) To use a "monitoring robot" that test the applications before the the real robots are executed. Is an option but maybe too manual
3) To use a commercial tool design for this feature: This would be great but I´m not aware of any exiting tool
So what I would like to ask is, how do you face this situation? Do you use any of the previous options? any other option?
Best regards,
Félix
------------------------------
Félix Granados
------------------------------
