After Successful login into SAP application you will get a different screen. Use Element Exist activity to identify any unique and stable element which is exist after successful login.
Element Exist activity will give a Bool(True/False) value as output. Use if condition or flow decision to check element exist value is true or not.
If it is true then proceed with Enter in to QRH and in else block raise an exception/send mail as per your requirement.
To capture any Generic Exceptions you can use Try Catch activity where you can put your code inside Try and exceptions will get capture in Catch block.
In order to stop the workflow if any error occurs abruptly, try to implement all the workflow that you mentioned inside a Try part of Try Catch block buddy.
and if any error occurs it will go to the catch block where you can use Terminate Workflow activity to stop the workflow buddy
Simple two steps …isn’t it…
I have added the exception handling. Generic exception(sys.exception ) and the Selector not found, file not found etc.
But what i am facing in real time is different. some times some different types of bugs are coming , they are throwing the different screens or dialog boxes , so i dont no what to be done for this. Well if i get like this then in Prod the BOT will get broken.
So this is what i am asking how to resolve it…
ex:
for this error i have to click - OK button. well i have to go for the unattended BOT
ex2:
Buddy @Seem
no worries
May i know why you are using start process
anyhow
if you want to use kindly check whether the file path mentioned in the start process in correctly entered without any typo mistake…
Kindly check this and let know buddy…but why start process …
Cheers @Seem