Posted: 17 Mar 2017 3:34 EDT Last activity: 6 Nov 2018 20:02 EST
Problem with Exit point in automation
I am raising the event in my automation and then after firing raising event, my automation is not doing further operation. please guide me for further solution. If after raising the event I can do further operation or automation then my problem will be resolve. I will not face problem 2
To over come I have done some work around, but then it leads to another issue, that is its not exiting from Automation.
As a solution I tried below things:
Raising the Event like below:
it was opening some pop up, so using Created event of that pop up
Then I want to exit from the automation ,but its holding the thread I believe.
Exit is not hitting after Created Event.
Please help me on this ASAP.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
If you are expecting a created event to occur and want to handle it in the same thread you need to use a WaitForEvent. This allows you to wait on the current thread. WaitForEvent is accomplished by dropping the Created event on the automation surface, right-click on it and choose Wait for this event. From the Setup yellow dot do the actions that will cause the event to happen.
It looks like you have to many execution paths on your automation as well. If you are exiting from an Exit Point (Exit1 or Exit2) then you should not exit from True and False or vice versa.
Thank you for your response, I will try it out and let you know. As Exit was not working for me, I tried with different exit path. I prefer to go with True/False rather then exit.
As mentioned in Problem 1, after raising the event my automation is not doing further operation, to resolve that issue I tried Created event. but I feel that's not real solution. Could you please tell me is there any way I can run my automation after raising the event?
I don't want to go for Created event approach. If you can help me on raising event then it would be helpful.
I really don't understand what you are trying to do. If you are trying to click a row in a table, you should use PerformClick on a control that is clickable. What does your RuntimeLog show happened? That is the best way to determine what executed. Normally, after doing a PerformClick execution should continue. If you are expecting a created event to occur at this point and need to wait for it to happen, then using the WaitForEvent is the proper way to go.