- 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
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- 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
- 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
JxBrowser applications troubleshooting
Selectors are natively generated for applications which rely on the JxBrowser, without having to install any extensions. Bear in mind that JxBrowser is not a stand-alone application, but a library which integrates Chromium in Java applications. Therefore, unpredictable issues can be encountered, depending on how this library is integrated in its host application. Currently, there are some automation limitations, as follows:
We highly recommend to avoid using the Recording wizard when building your automation projects, as it is not currently supported.
When building your automation projects, it is recommended to avoid using the Select Item and Select Multiple Items activities.