The UI elements change position dynamically and sometimes the XPath/selector fails, causing the bot to break. What are the best practices to make Surface Automation more stable and reliable in such dynamic UIs?
Surface Automation is generally recommended when the UI is highly dynamic or when working in restricted environments like Citrix or remote sessions where normal selectors (XPath/CSS) are not reliable.
Since UI elements may change position frequently, Surface Automation works using image recognition. It searches for a specific image or visual pattern on the screen and then performs the required action. Instead of depending on the DOM structure, it identifies the element visually.
You can use the Surface Action step by providing a template image and configuring the required target image. Based on that match, multiple mouse actions such as click, double-click, right-click, drag and drop, or hover can be performed.
1 Like
