A dynamic selector incorporates variables or arguments (e.g. {{variableName}}) to match UI elements whose attributes change at runtime (dates, dynamic database IDs, invoice numbers). To make brittle selectors resilient: 1) Open UI Explorer and identify stable parent tags, 2) Uncheck unstable dynamic attributes (like auto-generated GUIDs or 'idx'), 3) Replace dynamic characters with wildcards ('*' for multiple characters, '?' for single), 4) Anchor to stable adjacent labels, 5) Use modern Unified Target with Fuzzy selectors and Computer Vision fallback.

A Full Selector contains the top-level window tag (e.g. <wnd app='notepad.exe' ... />) and works independently anywhere on the screen without needing a parent container. A Partial Selector omits the top-level window tag because it inherits the window context from its parent container (Attach Window / Attach Browser / Use Application/Browser). Partial selectors are preferred inside workflows because they run faster, avoid window re-attaches, and keep code modular.

1) Simulate Click/Type: Communicates directly with the application's underlying technology via the browser DOM or Win32 API. Runs 100% in the background, does not move the mouse, fastest and most reliable, works on locked screens (does not support hotkeys). 2) SendWindowMessages: Sends Windows messages directly to the target window handle. Works in the background and supports hotkeys, but doesn't work on all modern web controls. 3) Hardware Events (Default): Moves the physical mouse cursor and sends physical keystrokes. Slowest, cannot run in the background, and will fail if a user touches the keyboard.