- 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
- Control Flow
- Object Repository
- Logging
- The ScreenScrapeJavaSupport Tool
- About the ScreenScrapeJavaSupport Tool
- Argument Descriptions for the ScreenScrapeJavaSupport Tool
- Studio testing
- 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
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User
Argument Descriptions for the ScreenScrapeJavaSupport Tool
The ScreenScrapeJavaSupport tool can be used to install or remove the Java extension from all fixed drives, default, or custom Java locations. Whenever you uninstall the Java extension with this tool, its path is kept track of, unless removed with the /forget argument.
To use the tool launch an elevated instance of the Command Prompt and navigate to the tool location by using the cd C:\Program Files\UiPath\Studio\UiPath\JavaSupport command. You can use it with the following arguments:
| Argument | Description |
|---|---|
|
|
Reinstalls the Java extension from all the Java versions that are currently installed. Can be used with the Examples:
|
|
|
Uninstalls the Java extension from all the Java versions that are currently installed. Can be used with the Examples:
|
|
|
Specifies the path of an installed Java version. Valid with the Examples:
|
|
|
Autodetects Java installations on all fixed drives. Valid with the |
|
|
Autodetects 32-bit and 64-bit Java installations in Program Files folders. Valid with the |
|
|
Turns off all message boxes. Valid with the |
|
|
Forgets all the location where the Java extension was installed. Valid with the |
|
|
Offers details about each installed Java version, as well as a cumulative status of all the installed Java versions. Displays
the default 32-bit and 64-bit Java installations if present on the system. Shows the history of uninstalled Java versions
(if the |
|
|
For the current Windows user and current session, scans all the processes with a corresponding UI and which have the Example:
|
|
|
Displays a list of all supported commands. Example:
|