- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
Full versus partial selectors
Target definition in UI Automation Modern activities separates the top-level window selector from the element selector:
- Window selector - Full selector for the application window.
- Strict selector - Partial selector. A strict selector is the precise string that matches exactly one specific on-screen UI element.
- Fuzzy selector - Partial selector. A fuzzy selector allows the robot to find a UI element by using a fuzzy matching algorithm, which can identify elements even if the selector doesn't contain an exact match for the attributes.
Full selectors contain all the elements needed to identify an UI element, including the top-level window.
The top-level window is defined by a full selector that can be found in the Selector property in the Use Application/Browser scope.
Example of a full selector for the Notepad window:
Partial selectors do not contain information about the top-level window.
Activities containing partial selectors are enclosed in a container (Use Application/Browser) that defines a full selector of the top-level window.
The UI element full definition is determined by merging the Window selector with the Strict selector/Fuzzy selector.
Example of a partial selector for the editable panel in Notepad:
Selector Editor and UI Explorer display the full selector, not just the partial one. However, only the elements belonging to the partial selector can be edited, the window selector is grayed out and read-only.
