Skip to main content

Hi everyone,

I’m automating Oracle Fusion and running into trouble with the “Query By Example” (QBE) toggle button. When I capture it with Recorder in Automation Anywhere A360, it comes through as an HTML Link instead of a true button.

In DEV, my bot works (with Generative AI fallback), but in TEST it fails to find the element and the Gen AI fallback doesn’t work either.

What I’ve tried so far:

  • Cleared all dynamic properties except DomXPath.

  • Created custom XPath using only stable attributes

  • Also tried targeting by alt and aria-pressed.

Issues:

  • A360 still often triggers Generative AI fallback, even with clean XPath.

  • The toggle appears in capture as an “HTML Link” (anchor tag <a>), not a button.

  • Randomized Oracle IDs (_FOpt1:...) break any capture that depends on them.

Question:

  • Has anyone successfully stabilized the QBE toggle (or similar Oracle links acting as buttons) across multiple Oracle environments?

  • Is there a recommended property or Recorder configuration (besides DomXPath) that works best here?

  • Should I expect it to remain listed as “HTML Link,” or is there a way to force A360 to recognize it more like a button?

Any guidance from others who’ve handled Oracle toggles in AA would be much appreciated!

Wow, ​@loisfreeman! You’ve used a majority of my tricks!

Other possible tricks:

  • Try using a Left Click instead of a click. This moves the mouse to the control and simulates pressing the mouse button.
     
  • Mouse clicks at coordinates. Yes, mouse clicks are position and resolution dependent. But they work, even if they make you feel gross for using them.   😅
     
  • Keystrokes. Find a control, like a text box, that is next to the button and set the focus to it with a Recorder: Capture, Click. Then use Simulate Keystrokes to send a tab (or multiple tabs) to move focus to the button. Press the button using a Simulate Keystroke with ENTER or a space.
     
  • Run JavaScript. Since you are well-versed in XPath, consider using JavaScript to “click” the button.
document.evaluate("//buttonv@aria-name='Click me']", document, null, XPathResult.FIRST_ORDERED_NODE_TYPE, null).singleNodeValue.click;

Anyone else care to jump in? ​@LegacyDevMaster123 

QBE (Query By Example) is a particularly tricky case because it is either on or off (pressed = true or false) and it doesn’t revert back to off by user after being run once.  I’m running an If statment on it, but the bot can’t consistently even find it, it seems to have too many dynamic links.

Reply


Terms & ConditionsCookie settings