At the moment I use conditional waits in almost every action where I need to press a button or something.
Basically I use the conditional wait to determine if the button is even there. And if its there. Blue Prism should press it.
I got an Internetexplorer Application that I interact with and I tried all the different spy modes so far:
IE HTML Mode, UI Automation and Accessibility mode
I handstopped the time how long blue prism needs to find a certain button.
With HTML its about 13secs, with Accesibility also 13 secs and with UI Automation 6 secs.
It takes a really long time ... and now when I use the conditional wait before the press button navigate stage I have doubled the amount of "waiting" time ...
Isn't there a better way to make this ?
At the moment our robot makes about 250 cases a day and if I can shave down these times I think I can make a huge improvement there.
Basically I use the conditional wait to determine if the button is even there. And if its there. Blue Prism should press it.
I got an Internetexplorer Application that I interact with and I tried all the different spy modes so far:
IE HTML Mode, UI Automation and Accessibility mode
I handstopped the time how long blue prism needs to find a certain button.
With HTML its about 13secs, with Accesibility also 13 secs and with UI Automation 6 secs.
It takes a really long time ... and now when I use the conditional wait before the press button navigate stage I have doubled the amount of "waiting" time ...
Isn't there a better way to make this ?
At the moment our robot makes about 250 cases a day and if I can shave down these times I think I can make a huge improvement there.
Attachments
Last edited: