studio
2023.4
false
- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- 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
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- About the WebDriver Protocol
- Configuration Steps
- Known Issues and Limitations
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Studio User Guide
Last updated Dec 17, 2024
Known Issues and Limitations
When you build your browser automation projects via the WebDriver protocol you need to take into consideration the following:
- Selectors for UI elements inside iframes are not validated. It is recommended to avoid iframes when you build your automation project. This occurs when element identification is done via the browser extension and selector validation via the WebDriver protocol.
- A browser automation created with the WebDriver protocol always creates a new browser session. This means that saved cookies or saved browser data are not taken into consideration when you build your automation project.
- If a selector is not found for a browser with multiple tabs opened, the execution constantly switches between them. In this scenario it is recommended to create your automation project on a single browser tab. This effect is only noticeable during visual browser automation.
- Headless automation does not rely on visual elements. As such, the WebDriver protocol doesn't actually open a visible browser window when it is used in Headless mode. Because of this, Headless automation cannot function with some activities which use hardware events (such as Click or Type Into) in their default state. They must be configured to use the SimulateClick, SimulateType, or SimulateHover properties, or the Send Window Messages property.
- Activities which interact with images (such as Click Image or Find Image) are not supported because they rely on the browser window itself.
- Events monitoring (such as Click Trigger or Hotkey Trigger) is not supported, because they rely on hardware events.
- Using
<WND>tags in the Close Application activity only closes the browser session and not the corresponding webdriver process. It is recommended to use<HTML>tags instead. - When using Chrome or Firefox, the browser window opened via the WebDriver protocol always opens in the same visual space and with the same size specifications. Moreover, some websites have adaptive page layout and this can lead to invalid selectors when the window size is changed. In this regard, it is recommended to use the default browser window size when you create your automation project.
