Hi Team,
We are Automating adding of the Components in Adobe Experience Manager.
Currently we are facing challenge in clicking of the Components, where Ui Path is not able to identify overlay Object loading Run time.
Need help here
Adobe Experience Manager renders overlay components dynamically at runtime, so UiPath cannot reliably identify them with standard selectors.
What works:
Use relative selectors / Anchor Base instead of full selectors
Add Check App State / Element Exists before clicking
If the overlay is not in DOM or is canvas-based, use Computer Vision / Click Image
This is an AEM UI behavior, not a UiPath issue.
Welcome to the community
can you show a screenshot of the issue
also for most of such applications loading components via menu/shortcut or via loading a csv works..try those ways as well
cheers
Hi Anil.
PFB Screen Shot. Currently through Ui path we are not able to find the Component which is mentioning tc001.
for now can you indicate anything on application from ui explorer
Then on left top menu (selector tree) you would get all elements that are present may be hidden as well…try to expand and use the highlight icon so that whe you click on a elment it highlights and shows which element it is…try finding if you are able to find from there
cheers
- Use UI Explorer and anchor on a stable parent element
- Switch selectors to wildcards for dynamic IDs/classes
- Try Click Image / CV Click instead of selector-based click
- Add wait for attribute / delay until overlay fully loads
- If available, use keyboard shortcuts or JS injection (last option)
- Use relative selectors or Anchor Base instead of full selectors
- Wait for the overlay to load using Check App State / Element Exists
- Add retry logic to handle dynamic UI
- If the element is not exposed in the DOM, then use Computer Vision or Image-based click as a fallback
These methods usually resolve AEM overlay interaction issues.