I'm trying to capture few buttons but they aren't being recognized in A360.

no results.

Hi @sirispandana velagala​ ,

Could you pass this XPath into the Inspection Window just to validate whether it returns a unique match?

//button[@id='ext-gen426']

Kind Regards,

Ashwin A.K

Hi @sirispandana velagala​ ,

Then that means the XPath requires a bit more polishing, would be so kind as to include a larger snippet of the DOM so that I can help you with it?

Kind Regards,

Ashwin A.K

Or how about this:

//button[.='Next'] -> Does this return a unique match?

Kind Regards,

Ashwin A.K

This returns a unique match.

This is how I set the attributes. Still no luck.

figured out how the keystrokes are working.

gonna try to use them.

Thanks !!

Hi @sirispandana velagala​ ,

I usually keep only the DOMXpath checked, and the rest inactive and it works out fine for me.

Its difficult to say for sure what the issue is unless I have access the the instance itself, but I'm glad you were able to come up with a solution on your own!

Kind Regards,

Ashwin A.K

Understood, some elements are tricky to work with.

Here is something else you could try, simply Capture the element and then pass in the DOMXpath and see if the bot is able to interact with it.

If that works, then slowly start unchecking the Object Properties one by one, and run the process each time just to check which property is responsible for successfully targeting the element of interest.

In my experiments, I noticed that elements encased inside frames require the HTML HasFrame to be enabled.

It could be different for you, its all trial and error.

If nothing else work, then you have to rely on Simulate Keystrokes.

Kind Regards,

Ashwin A.K

I've tried keeping only DOMXpath active as well, but the application has IFrame which is messing with the DOMXpath.