Spying a Hyperlink on a Web Browser not working

[Fran.Woodcock]

Hi all, please help!

I am trying to spy a hyperlink on a Web browser using Edge and although the spying is successful, when I run the process from the start, there is an exception thrown to say the element could not be identified (when I have literally just spied it!).  I opened the extended modeller and this is what I see:

I have set the element type to Hyperlink in the Application Modeller and it only likes it and works when I spy it mid way through and set the run stage from the wait stage right before it.  IT never works if I run the process from the start.

I just don't know what I'm doing wrong here...

Many thanks for any help!

Fran

------------------------------
Fran Woodcock
------------------------------

[harish.m]

Hi fran Woodcook,

I verified the browser mode, as you mentioned i got similar error , though I have added wait stage with parent Document loaded in the wait stage. 

So if you add wait stage after launching the application and interacting with login button that would  work if it is not working i would suggest to  add some unconditional wait time though in general i wont recommend to add additional wait time

Other approach is to respy with  UIA mode some thing like below and add condition wait time that works
I selected below attributes in app Modeller

------------------------------
-----------------------
If I answered your query. Please mark it as the "Best Answer"

Harish Mogulluri
Lead developer
America/New_York TX
------------------------------

[michaeloneil]

Hi @Fran.Woodcock

I cant see the image you loaded but from the description your element is likely dynamic in nature meaning the attributes you use to spy it are changing on the website every time you refresh or restart the web page e.g. table number in the attribute path might be 1 when spied and 2 the next time the page is opened. If you spy it using a different spy type or play around with the attribute selections to get a consistent match then you should be able to resolve this.

------------------------------
Michael ONeil
Technical Lead developer
NTTData
Europe/London
------------------------------

[Fran.Woodcock]

Hi Michael,

Thanks for your suggestion, I couldn't see an attribute path being available when I spied the hyperlink and changing the Match Index didn't help either. 

In the end I changed the URL - I was only using the one I was using because I was having issues with the URL before!

So I don't have to even consider the Log in Agent link now.

Thank you though, I will remember the attribute path from hereon-in!

Thanks

Fran

------------------------------
Fran Woodcock
------------------------------

[Fran.Woodcock]

Hi Harish

Thanks fro your suggestion, I had already built in pauses and waits to let the pages load.  I tried your example though and it didn't help. In the end I changed the URL to good effect.  The URL was being used because I was having issues previously which are now resolved so I don't need to even consider the Agent Log In hyperlink now. 

Thanks 

Fran

------------------------------
Fran Woodcock
------------------------------