UI Automation activities

Last updated Feb 19, 2026

UI Automation Project Settings

These project settings apply for Modern activities in Cross-platform projects.

Use Project Settings to configure changes at the project level. These global settings impact all activities in the package that have the properties listed below. For more information, see Configuring Activity Project Settings.

Important:

The properties configured in Project Settings only take effect in the activities of the workflow if their properties have not been edited. Editing properties manually no longer applies the project settings to them.

To configure the UI Automation project settings, follow these steps:

In the Project panel, go to Project Settings.
Navigate to Activities Settings > UI Automation.
Modify the settings according to what you want to change.
Click OK to save changes.

You can reset all settings to their default values or copy all values between the debug and production fields using the Bulk Actions drop-down menu at the top of the window.

Generic

The settings below apply to UI Automation Modern activities in Cross-platform projects that have either one of the following properties.

Property name	Description
Delay after (seconds)	Delay time between the current activity and the next activity.
Delay before (seconds)	Delay time between the previous activity and the current activity.
Timeout (seconds)	How long to wait for the current activity to be executed before throwing an error.
Wait for page load	Before performing the action, wait for the application to become ready to accept input. The following options are available: None - Does not wait for the target to be ready. Interactive - Waits until only a part of the application is loaded. Complete - Waits for the entire application to load.
Capture screenshots	Dictates if screenshots are captured at design time by all the activities that support this feature. If the setting is set to false, the Remove informative screenshot option from the context menu is disabled.
Alter disabled element	If set to True , the Select Item action is executed even if the specified UI element is disabled. This property does not apply if the Input Mode property is set to Hardware Events .
Wait for primary targeting method until timeout	If set to True , this setting allows the primary targeting method to consume its full timeout until any fallback targeting method can be used.
Enable Java automation (preview)	If set to True , you can indicate Java applications. If set to False , you can indicate only Chrome browser windows.
Automatically add UI elements to Object Repository	If set to True , all UI elements are automatically added to Object Repository.

Targeting methods - Web browsers

The settings below apply to indicated targets and anchors for web applications.

Property name	Description
Input mode for Edge, Chrome	Select how to execute the action: Simulate - Simulates the click using accessibility APIs. Recommended in browser automation, Java apps, or SAP. More reliable than Hardware Events . Works even if the target application is not in focus. Test if your target application UI element supports this. ChromiumAPI - Performs actions using debugger APIs. Works for Chromium elements only. Sends all text in one go. Works even if the target application is not in focus. For more details, check out the Chromium API page. Note: When the browser is started with Chromium API, a ribbon shows up stating that the browser started in debug mode. This message does not appear if the extension is installed via policy.
Selector - default find type	Select the default type of find used by the UI element selector. The following options are available: Disabled - Does not use the Selector targeting method to find the UIelement. One match - Uses an exact-match approach. This method ensures precise element identification, but may fail if these attributes change dynamically or if the UI lacks stable identifiers. All matches - intentionally produces multiple matches. It is designed to always be used with anchors to refine selection, making it more resilient to slight UI changes while ensuring contextual accurracy. Auto - Automatically chooses the most appropriate find type of the UI element selector: One match or All matches . The default value is All matches .
Computer Vision	If set to True , uses the Computer Vision method. The default value is True .
Ignore selectors with IDX / tableRow / tableCol	Disable the full selector if the target selector has a `tableRow` , `tableCol` , or an `idx` attribute with a value higher than 1 and anchors exist.

Targeting methods - SAP

The settings below apply to indicated targets and anchors for SAP.

Property name	Description
Input mode	Simulate - Simulates the click using accessibility APIs. Recommended in browser automation, Java apps, or SAP. More reliable than Hardware Events . Works even if the target application is not in focus. Test if your target application UI element supports this.
Selector - default find type	Select the default type of find used by the UI element selector. The following options are available: Disabled - Does not use the Selector targeting method to find the UIelement. One match - Uses an exact-match approach. This method ensures precise element identification, but may fail if these attributes change dynamically or if the UI lacks stable identifiers. All matches - intentionally produces multiple matches. It is designed to always be used with anchors to refine selection, making it more resilient to slight UI changes while ensuring contextual accurracy. Auto - Automatically chooses the most appropriate find type of the UI element selector: One match or All matches . The default value is One match .
Computer Vision	If set to True , uses the Computer Vision method. The default value is False .
Ignore selectors with IDX / tableRow / tableCol	Disable the full selector if the target selector has a `tableRow` , `tableCol` , or an `idx` attribute with a value higher than 1 and anchors exist.

Targeting methods - Java

The settings below apply to indicated targets and anchors for Java applications.

Property name	Description
Input mode	Simulate - Simulates the click using accessibility APIs. Recommended in browser automation, Java apps, or SAP. More reliable than Hardware Events . Works even if the target application is not in focus. Test if your target application UI element supports this.
Selector - default find type	Select the default type of find used by the UI element selector. The following options are available: Disabled - Does not use the Selector targeting method to find the UIelement. One match - Uses an exact-match approach. This method ensures precise element identification, but may fail if these attributes change dynamically or if the UI lacks stable identifiers. All matches - intentionally produces multiple matches. It is designed to always be used with anchors to refine selection, making it more resilient to slight UI changes while ensuring contextual accurracy. Auto - Automatically chooses the most appropriate find type of the UI element selector: One match or All matches . The default value is One match .
Computer Vision	If set to True , uses the Computer Vision method. The default value is True .
Ignore selectors with IDX / tableRow / tableCol	Disable the full selector if the target selector has a `tableRow` , `tableCol` , or an `idx` attribute with a value higher than 1 and anchors exist.

Application/Browser

The settings below apply to the Use Application/Browser activity. Settings changed here take effect at Runtime if the corresponding property is left blank in the activity.

Property name	Description
Open	Defines whether to open the target application before executing activities in it. The following options are available: Never - Never start/open a new application instance or browser window. If not open - Open a new application instance or browser window, if the selector does not match any existing instance. Always - Always open a new application instance or browser window. When opening a new instance, the file path and arguments are used to launch the application.
Close	In which cases to close the target application after executing activities in it. The following options are available: Never - Do not close the application instance or browser window after executing the activities in scope, even if it was opened by the Use Application/Browser activity. If opened by App/Browser - Close the application instance or browser window only if it was opened by the Use Application/Browser activity. Always - Always close the application instance or browser window after executing the activities in scope.
Window attach mode	Specifies the default window attach mode used by newly added Use Application/Browser activities. The following options are available: Application instance - Inner activities will search in the indicated application instance, including all parent and child windows (alerts, popups, etc). Other instances of the application are excluded. Single window - Inner activities will search only in the indicated window.
User data folder mode	The user data folder mode you want to set. It is used to start the browser with a specific user data folder. Automatic - Picture In Picture mode uses a different folder than the default mode, automatically generated if User data folder path is not set. Default folder - Uses the default browser folder, no matter if it runs in the main or PIP session. Custom folder - Uses the folder specified in User data folder path or an auto generated path if User data folder path is not set.
User data folder path	The path to the user data folder that the browser uses.
Open browser timeout (seconds)	Configure the browser startup timeout.
Dismiss Alerts	Enable auto-dismissal of JavaScript alert dialogs.
Dismiss Confirms	Enable auto-dismissal of JavaScript confirm dialogs.
Dismiss Prompts	Enable auto-dismissal of JavaScript prompt dialogs.
Confirm dialog response	Set the response to JavaScript confirm dialogs: Cancel or OK .
Prompt dialog response	Set the response to JavaScript prompt dialogs: Cancel or OK .
Prompt response text Enable auto-dismissal of JavaScript alert dialogs.	Set the text response for JavaScript prompt dialogs.

Keyboard Events

The settings below apply to the Type Into and Keyboard Shortcuts activities.

Property name	Description
Type Into - Click before typing	Whether to click the specified UI element before typing the text, and the type of click to perform. The following options are available: None Single Double
Type Into - Empty field	Whether to delete the existing content before typing the text, and how to clear the field. The following options are available: None Single line [End, Shift + Home, Del] Multi line [Ctrl +A, Del]
Type Into - Clipboard	Indicates whether the clipboard is used to type the given text. The following options are available: Never – Never use the clipboard. Always – Always use the clipboard. Whenever possible – Use the clipboard when possible. This depends on the OS and the text to be typed (e.g. if any special key is used, then the clipboard will not be used).
Keyboard Shortcuts - Delay between shortcuts (seconds)	Delay time between consecutive special keys.

SAP

Applies to any UI Automation activity during SAP automation.

Property name	Description
Enforce hard timeout (only for SAP WinGUI and GUI for Java)	Enforces a hard timeout for all activities performing SAP WinGUI or SAP GUI for Java automation.

ScreenPlay

The settings below apply to the ScreenPlay activity. Settings changed here take effect at Runtime if the corresponding property is left blank in the activity.

Property name	Description
Model	Indicates the underlying LLM used by ScreenPlay for task execution planning and reasoning. The following options are available: UiPath Screen Agent (with Gemini 2.5 Flash) Basic model Works best on browsers Uses a proprietary implementation based on the page's DOM, using Gemini Flash for reasoning and image understanding Moderately fast UiPath Screen Agent (with GPT-4.1) Standard model - for complex tasks Works best on browsers Uses a proprietary implementation based on the page's DOM and image understanding, using GPT-4.1 for reasoning Not very fast UiPath Screen Agent (with GPT-4.1 mini) Basic model - faster, cheaper Works best on browsers Uses a proprietary implementation based on the page's DOM and image understanding, using GPT-4.1 mini for reasoning Moderately fast UiPath Screen Agent (with GPT-5) Standard model - for complex tasks Works best on browsers Uses a proprietary implementation based on the page's DOM and image understanding, using GPT-5 for reasoning Slow UiPath Screen Agent (with GPT-5 mini) Basic model - faster, cheaper Works best on browsers Uses a proprietary implementation based on the page's DOM and image understanding, using GPT-5 mini for reasoning Moderately fast OpenAI - Operator Standard model - for complex tasks Works on any type of application, including image-based interfaces Uses OpenAI Operator, an image-based reasoning model. Likely the best of the bunch Slow Anthropic - Computer Use Standard model - for complex tasks Works on any type of application, including image-based interfaces Uses Anthropic Computer Use, an image-based reasoning model Slow
Type by clipboard	Indicates whether the clipboard is used for typing the given text. The following options are available: Never - Never use the clipboard Always - Always use the clipboard Whenever possible - Use the clipboard when possible. This depends on the OS and the text to be typed (e.g. If any special key is used, then the clipbaord will not be used)
Max number of steps	The maximum number of steps that ScreenPlay can take to achieve its goal.
Use DOM when available	Indicates whether DOM data will be used/sent to the LLM Model for applications where DOM can be extracted. DOM can be used only by UiPath LAM implementations. Disable if DOM-based targeting leads to incorrect element coordinates.
Logging	Specifies at what level the logs generated by the ScreenPlay activity are stored. The following options are available: Off Info Trace
Enable trace files	Specifies the type of trace files generated by the ScreenPlay activity. The following options are available: Disabled - No trace file will be saved/stored. Html - Html trace files will be saved/stored. Html and json - Html and main json trace files will be saved stored. Full - Html, main json and iteration json trace files will be saved/stored.
Trace files retention (days)	Number of days to retain traces before deletion. Set to 0 to keep the traces indefinitely.

Other Activities

The settings below apply to the Check App State, Extract Table Data, Highlight, Hover, Inject Js Script, Close Popup, and SAP Logon activities.

Property name	Description
Check App State - Timeout (seconds)	How long to wait for the target element to appear or disappear.
Extract Table Data - Delay between pages (seconds)	If the data spans multiple pages, how long to wait for each page to be loaded.
Highlight - Duration (seconds)	How long to highlight the target element.
Hover - Duration (seconds)	How long to hover over the target element.
Inject Js Script - Execution world	Applies the InjectJs.ExecutionWorld setting globally. For details, see the Inject Js Script activity.
Close Popup - Popup Appear Timeout	The amount of time (in seconds) to wait for a pop-up to appear.

Robot Logging

Information about the methods used to identify targets and anchors, and the performance of each method at runtime can be saved in the Robot execution logs. The options apply to all supported activities.

Property name	Property Description	Impacted Activities
Log target & anchor search steps	Specifies at what level we store the logs for the methods used to identify targets and anchors. The following options are available: Off Info Trace	Check/Uncheck Check App State Click Extract Table Data Get Text Highlight Hover Keyboard Shortcuts Select Item Type Into
Log targeting methods timings	Specifies at what level we store the logs for the performance of each targeting method. The following options are available: Off Info Trace	Check/Uncheck Check App State Click Extract Table Data Get Text Highlight Hover Keyboard Shortcuts Select Item Type Into
Log audit information	Specifies at what level the logs generated by the Use Application/Browser activity are stored. The following options are available: Off Info Trace	Use Application/Browser