studio
2023.10
false
- 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-021 - Hardcoded Timeout
- 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
- Coded automations
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- About Native RDP Automation
- Configuration Steps
- How Native RDP Automation Works
- Example of RDP Automation
- Known Issues and Limitations
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities packages and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Chrome Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Edge Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for VMware Horizon
- SAP Solution Manager plugin
- Excel Add-in
- Troubleshooting
Studio User Guide
Last updated Nov 4, 2024
How Native RDP Automation Works
When you are done installing the UiPath Remote Runtime component and the Windows Remote Desktop Extension, individual UI elements are natively detected for applications on Remote Desktop machines.
This is what a generated selector for Notepad opened on a Remote Desktop machine looks like:
<rdp app='mstsc.exe' cls='TscShellContainerClass' title='* - Remote Desktop Connection' />
<wnd app='notepad.exe' cls='Notepad' title='Untitled - Notepad' /><rdp app='mstsc.exe' cls='TscShellContainerClass' title='* - Remote Desktop Connection' />
<wnd app='notepad.exe' cls='Notepad' title='Untitled - Notepad' />This is what a generated selector for Notepad opened as a local application looks like:
<wnd app='notepad.exe' cls='Notepad' title='Untitled - Notepad' /><wnd app='notepad.exe' cls='Notepad' title='Untitled - Notepad' />The only difference between the two selectors is the
<rdp> tag, which contains all the details of the corresponding RDP connection. It gets automatically added when selecting UI elements
from an application opened on a Remote Desktop machine.
With the help of native RDP support, you can do the following:
- Generate selectors for applications opened on a Remote Desktop machine.
- Use the activities from the UiPath.UIAutomation.Activities package (such as Click, Type Into, and more).
- Use mouse and keyboard monitoring events activities.
- Use Data and Screen Scraping Wizards.
- Automate browsers.
The UiPath Remote Runtime is installed on the Remote Desktop machine, while the Windows Remote Desktop Extension on the client machine. The communication between these components is done through Remote Desktop Protocol. For more information, see Remote Runtime architecture.
