Recorder native fallback - When you try to automate dynamic web applications where the properties of the controls change frequently, the Recorder might fail to automate such applications as the DOMXPath property value changes with every page refresh. To automate such scenarios, enable the Recorder native fallback support.

When you try to automate dynamic web applications where the properties of the controls change frequently, the Recorder might fail to automate such applications as the DOMXPath property value changes with every page refresh. To automate such scenarios, enable the Recorder native fallback support.

Recorder native fallback feature generates multiple DOMXPaths while capturing the object which are then stored and validated to ensure if they can be used for the current business application. Once the Generative Recorder verifies that a fallback DOMXPath can uniquely identify the target UI element, it conducts an additional validation step. This involves comparing other properties of the UI element. For instance, if the automated action involves data entry, the Generative Recorder ensures that the automation proceeds only if the fallback DOMXPath corresponds to a data entry input, such as a text box, and not to buttons or labels. The reliable and relevant DOMXPaths are then used for your automations. These alternative XPath expressions and object properties are captured at design time and are separate from the primary search criteria used during normal execution.

Native fallback triggers automatically when the primary search criteria do not match any element on the page; no manual intervention is required. There are no consumption limits; it runs without restriction. To use native fallback, you must capture (or recapture) the UI elements using the Recorder package 3.0.x or higher and browser extension 3.2.0.0 or higher.

Native fallback also reliably identifies HTML buttons and links using visible text and key attributes, ensuring stable automation even when the position of UI elements changes, and fails safely instead of clicking the wrong element when the original element is removed or hidden. This reduces automation breakages in modern web apps after UI updates or changes in dynamic attributes without requiring you to re-record existing automations.