- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Logging
- 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-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- 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
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Trigger-based Attended Automation
- Recording
- UI Elements
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- About Automating Citrix Technologies
- Configuration Steps
- Example of Automating a Citrix App
- Known Issues and Limitations
- RDP Automation
- VMware Horizon Automation
- Salesforce Automation
- SAP Automation
- macOS UI Automation
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- 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 Safari
- Extension for VMware Horizon
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Test Suite - Studio
- Troubleshooting
Known Issues and Limitations
With the help of UI Automation activities you can natively generate selectors for Citrix technologies and create your automation projects. There are, however, a few things to consider:
The Extension for Citrix is installed per machine and cannot communicate with the Citrix client (Citrix Receiver or Citrix Workspace) when it is installed per user. You need to install the Citrix client per machine before installing the UiPath Extension for Citrix.
Interactive selection with High DPI is natively performed in Citrix Apps. Please note that it is mandatory to restart your active Citrix sessions after you change DPI scaling options.
If you are using multiple displays with different DPI scaling options and you move the target window across the displays, UI element selection can appear offset. In this case, it is recommended to resize the target window and select UI elements again.
After you upgrade the Citrix Receiver to the Citrix Workspace, the UiPath Extension for Citrix is automatically uninstalled. In order to build selectors for Citrix technologies again, you need to reinstall the UiPath Extension for Citrix.
Please note that after upgrading to the Citrix Workspace v1810 the UiPath Extension for Citrix becomes corrupted. This is a known issue with this particular version of Citrix Workspace, and prevents you from opening any Citrix Apps. The following error message is displayed:
You might be having an issue with a Citrix virtual driver (UiPathPluginCitrix). Contact your system administrator for further
assistance.
To fix this issue, you need to reinstall the UiPath Extension for Citrix and then restart the Citrix Workspace.
Please note that after every upgrade or installation of the Citrix Receiver or Workspace the UiPath Extension for Citrix needs to be reinstalled.
The UiPath Extension for Citrix can not be installed for the Citrix Receiver for Universal Windows Platform. This also applies to Citrix Workspace for Universal Windows Platform. In this scenario, it is advisable to install the standard Citrix Receiver or Citrix Workspace instead.
If a Citrix App does not receive any input from the user for a while, the associated Citrix session enters the idle state and disconnects. The idle disconnect timeout value is configured on the Citrix application server, and is generally about 30 minutes.
By default, the Click and Type Into activities send hardware events to the Citrix App, just as a regular user would. This prevents the Citrix App from entering the idle state.
However, if you use only background automation (such as the Click activity with the SendWindowMessages property enabled) for more than 30 minutes, the Citrix App may enter the idle state, and the following message is displayed:
If you run into this issue, it is recommended to increase the idle timeout value on the Citrix application server.
