Cache location of Field After Wait Item

[TomCirone]

There are some busy applications (specifically in websites) where it takes a few seconds to find the field.  When you use a wait for stage, this time is then doubled.  If I say wait for Field X, Field X appears,it takes 3 seconds to find Field X and move to the next stage.  Then I say click field X: it searches for it for 3 seconds again, finds it, and clicks it.

It feels that after a wait stage it should cache the location (even if it's just for the next stage).  Even better it could see if any other action in the object page is going to that item and wait

I like to think of this similar to a Librarian with a card catalog ;
Customer: Do you have this book?
*Librarian searches catalog and finds item*
Librarian: Yes we do
*Librarian closes card catalog*
Customer: Where is it?
*Librarian searches catalog and finds item*
Librarian: Mystery section under Adams

[MarcoMatuttis1]

I have an application where all spymodes are pretty slow. It takes 6-12seconds to find a button depending on the spymode.

When I have a conditional wait to wait until the button is available I actually double the waiting time.

1. Blueprism waits in the conditional wait to find the button.

2. Blueprism waits the same amount of time to find the button again to then click it.

Would be better if Blueprism could click right away after the conditional wait.

[robert.nicklin]

Hello @MarcoMatuttis1,

Thanks for taking the time to raise an idea.

Having reviewed the content of this idea, I've realized it's actually a duplicate of another idea on the community with a higher number of votes. To centralize the discussion on this topic, I will merge this idea into the other idea shortly.

Regards,

Rob