Hi ​@ZaremPatricia Let me tag some folks who may be able to help!

​@Marc Mueller 

​@Vatsy 

Hey ​@ZaremPatricia , if the position is same on every instance, you can use Mouse → Move action and then when the option comes up you can perform the next operation, try it and let me know.

Hi ​@ZaremPatricia,

or if it is a web based task you can try with the correct DOMXPath...

How to use the developer tool in Chrome to get the DOMXPath I explain here:

Cheers

Marc

...or if it has the same appearance but a different location each time, you can use the Image Recognition package to get the coordinates of the button and use the Mouse package to move the mouse to the coordinates and click!

So many great options from ​@zaid.chougle and ​@Marc Mueller !

Hey ​@Lu.Hunnicutt! Thanks for the tag! Great answers by ​@zaid.chougle, ​@Marc Mueller, and ​@Aaron.Gleason here!

I just want to add one more option of using Simulate Keystrokes as the question says that unless the OP hovers over on a label with a Mouse the other option doesn’t come up.

You can use TAB key strokes to reach to the required option and then use RETURN keystroke to select the required option on the screen. This only applies if the label object remains at the same place each time you access it.

Hope this helps!

Thanks for all the advises. Tried to use the Call a JavaScript function from Browser package with the intention to pop up the menu instead doing the mouse movement (which didn’t work) and I got “The captured UI element in this application is not currently supported”.

I’m using AA Community Edition. Does the message could be to the app edition or would be something about how the website is designed/coded?

 ​@ZaremPatricia , The error is more likely related to how the website is designed/coded than the AA Community Edition. The website’s UI element may use non-standard technology, dynamic rendering, or event handling that AA Browser package can’t reliably interact with. The Community Edition supports the same Browser package actions as the enterprise version,

so the limitation isn’t edition-specific.

The Universal Recorder may help capture the hidden menu if you manually hover over the label to make it visible during recording. However, to reliably automate it, try:

1. Use Universal Recorder:
   • Start the Recorder in Universal mode.
   • Hover over the label to reveal the menu, then capture the desired menu option.
   • Test the bot to ensure it works consistently.
2. Use Simulate Keystrokes (e.g., {Tab}, {Down}) if the menu supports keyboard navigation.

If you test this and still face issues, let me know for a more targeted fix!

Hello ​@jasthi bhaskar 

Page doesn’t have map the keyboard navigation for the menu in matter.

When I run the bot (actions previously recorded using universal recorder) doesn’t reveal the menu either and the action executed is different that result I expect.

Would appreciate any other fix/idea/proposal you may have. Thanks!