UiPath Documentation
activities
latest
false

UI Automation activities

Update UI Element (former Set Value)

UiPath.Semantic.Activities.NSetValue

Description

Uses AI to seamlessly set a value on any input field: input box, drop-down, check box, radio buttons, date picker.

It can be used only on Chrome, Edge, Firefox, and Safari.

Uses the same functionality as Fill Form, but on element level.

Instead of using other activities for specific input fields (for instance, Type Into for input boxes, Check/Uncheck for check boxes, etc.), you can use a single generic Update UI Element activity. It can also deal with date pickers and groups of radio buttons.

This activity must be added inside a Use Application/Browser activity.

This activity is compatible with Object Repository.

Project compatibility

Windows | Cross-platform

Configuration

  • Indicate on screen - Indicate the UI element to use as target.
    After you indicate the target, select the plus button to access the following options:
    • Indicate target - Indicate the target again.
    • Edit target - Open the selection mode to configure the target.
  • Value - The value set on the field. This field accepts only String variables.
    If the indicated target is a checkbox, these are the accepted values:
    • True: "true", "yes", "checked", "x"
    • False: "false", "no", "unchecked"
  • Enable validation - Enables execution validation for the run-time value if the toggle button is set to On. An exception is thrown if the internal validation mechanism detects an invalid value after the execution. The default option is Off.

Properties panel

Target

  • Window selector (Application instance) - The selector for the application window (application/browser).
  • Semantic selector - A semantic description of the target.
  • Semantic selector model - Indicates the underlying LLM model used for semantic processing. It can be changed only from Project Settings > UI Automation > Semantic Selector.
    Available models: Gemini 2.5 Flash, Path Mini (see Project Settings for Semantic Selector).
  • Wait for page load - Waits for the application to become ready to accept input before performing the action. The options are:
    • None - Does not wait for the target to be ready.
    • Interactive - Waits until only a part of the app is loaded.
    • Complete - Waits for the entire app to be loaded.
  • Visibility check - When enabled, the activity also checks whether the UI element is visible or not. You can choose one of three options from the drop-down menu:
    • None - Does not check for visibility.
    • Interactive (for Fuzzy Selector) - Default option. Checks if the element is potentially visible, ignoring page scroll and obstructions by other apps, or the fact that the application is minimized. This check is useful when trying to ensure that you are not targeting invisible elements that exist in the DOM but are hidden.
    • Fully visible - Checks if the UI element is visible or not.
  • Responsive websites - Enables responsive websites layout.

Options

  • Model - The LLM model used to understand the target UI element and produce the value to set. It can be changed only from Project Settings > UI Automation > Semantic Activities > Update UI Element - Model.
    Available models (see Project Settings for Semantic Activities):
    • GPT-4.1
    • GPT-4.1 mini
    • GPT-5 mini
    • Gemini 2.5 Flash
    • Gemini 3.0 Flash Preview
    • Path Mini
  • Healing Agent mode - Configures the behavior of the Healing Agent for this activity, based on Governance or Orchestrator settings at process or job level.
    • Same as App/Browser - Inherits the configuration from the parent Use Application/Browser activity.
    • Inherit job settings - Applies the settings defined in Governance or in Orchestrator at the process or job level.
    • Disabled - Turns off the Healing Agent for this activity.
    • Recommendation only - Enables the Healing Agent to provide recommendations on how to fix UI automation issues on running jobs, but only if permitted by Governance or Orchestrator settings.
  • Continue on error - Specifies if the automation should continue even when the activity throws an error. This field only supports Boolean values (True, False). The default value is False. As a result, if the field is blank and an error is thrown, the execution of the project stops. If the value is set to True, the execution of the project continues regardless of any error.

Timings

  • Delay before - Delay (in seconds) between the time the previous activity is completed and the time this activity begins performing any operations. The default value is 0.2 seconds. Adding a delay between activities ensures that one activity has enough time to complete before the next activity begins.
  • Delay after - Delay (in seconds) between the time this activity is completed and the time the next activity begins any operations. The default value is 0.3 seconds. Adding a delay between activities ensures that one activity has enough time to complete before the next activity begins.
  • Timeout - Specify the amount of time (in seconds) to wait for the activity to be executed before throwing an error. The default value is 30 seconds.
  • Description
  • Project compatibility
  • Configuration
  • Target
  • Options
  • Timings

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated