--- title: Use the Universal App Connector description: Create automations for your Windows, Java, Google Chrome, and Edge browser-based applications by using the Universal App Connector \(UAC\). Configure the applications from a single, unified connector and capture the screens and elements or screen controls such as check boxes, and buttons. Use the methods of these screens and elements to build your automation. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/integrate-applications/configure-uac.html release: australia topic_type: task last_updated: "2026-03-12" reading_time_minutes: 8 breadcrumb: [Universal app connector, Connectors, Automation components, RPA Desktop Design Studio, Robotic Process Automation \(RPA\) Hub, Workflow Data Fabric] --- # Use the Universal App Connector Create automations for your Windows, Java, Google Chrome, and Edge browser-based applications by using the Universal App Connector \(UAC\). Configure the applications from a single, unified connector and capture the screens and elements or screen controls such as check boxes, and buttons. Use the methods of these screens and elements to build your automation. ## Before you begin Add the Universal App Connector plugin from the Plugins Manager before using the connector. For more information about adding the SSH plugin, see [Manage plugins in RPA Desktop Design Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/install-plugins-rpa-studio.md). Verify that you have open or active Windows, Java, Google Chrome, or Edge applications. Role required: None ## Procedure 1. In the Toolbox pane, navigate to **Connectors**, and drag **Universal App Connector** to **Global Objects** in the Project Explorer pane. The connector is added as a **UniversalApplication** object under **Global Objects**. 2. To use the methods at the **Universal App Connector** connector level, double-click the **UniversalApplication** object. |Method name|Reference| |-----------|---------| |**Click**|[Use the Click method for Universal App Connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/use-click-method-uac.md)| |**GetValue**|[Use the GetValue method for Universal App Connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/use-getvalue-method-uac.md)| |**SetValue**|[Use the SetValue method for Universal App Connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/use-setvalue-uac.md)| |**Start**|[Use the Start method for Universal App Connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/use-start-method.md)| |**WaitForAnyScreen**|[Use the WaitForAnyScreen method for Universal App Connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/use-the-wait-for-any-screen-method.md)| For example, the Start method is used if you want the browser or application to start before interacting with any application screens or elements. The methods appear in the Object Explorer pane. 3. To configure the screens and elements in the UAC, do the steps. 1. Under Global Objects, right-click **UniversalApplication** and select **Configure**. 2. On the Configure screens and elements window, select the **Choose from an open window** drop-down \(\[Omitted image "UAC-connector-select-application-icon.png"\] Alt text: Choose from an open window drop-down.\) and select an application screen. \[Omitted image "uac-connector-open-apps.png"\] Alt text: Open applications. **Note:** - If no supported applications are open, the `App window not found message` is displayed. - To display newly opened application screens on the list, select the Click to refresh windows icon \(\[Omitted image "refresh-uac-list.png"\] Alt text: Click to refresh windows icon.\). 3. To filter the opened applications by their type, select the **All** filter application type icon \(\[Omitted image "uac-connector-all-applications-filter.png"\] Alt text: Filter application type icon.\) and select All or the application type. For example, if you select **Chrome**, only Google Chrome web pages appear in the **Choose from an open window** list. For example, if you select **Windows Application**, only Windows screens appear in the **Choose from an open window** list. \[Omitted image "filter-app-type-uac.png"\] Alt text: Filter the application types. 4. To add the selected application screen, select **Add screen**. After you do this step, you can capture the screen elements to perform actions. The application screen appears under the Screens and elements pane. \[Omitted image "uac-connector-application-screen-added.png"\] Alt text: Application screen name appears under Screens and elements. 5. To capture the elements from the screen, under the Screen and elements pane, right-click the added screen and select **Capture Element**. \[Omitted image "uac-connector-capture-window.png"\] Alt text: Capture Element option. The focus is set on the application screen that you had captured and the capture elements dialog appears. For example, when you are capturing elements of a Windows application such as Notepad. If you select the **UIA** mode \(UI Automation\), the scroll bar of the Notepad is also captured. \[Omitted image "uac-windows-app-uia-mode.png"\] Alt text: UI Automation mode of the Windows application, such as Notepad. If you select the **AA** mode \(Active Accessibility\), the scroll bar of the Notepad is not captured. \[Omitted image "uac-windows-app-aa-mode.png"\] Alt text: Active Accessibility mode of the Windows application, such as Notepad. 6. To use the methods at the **Universal App Connector** connector level for the two modes, UI Automation and Active Accessibility, double-click the **UniversalApplication** object. For more information about the methods for UI Automation mode and Active Accessibility mode, see [Methods of UI Automation mode and Active Accessibility mode](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/uac-windows-uia-aa-methods.md). The methods appear in the Object Explorer pane. 4. Do any of the following options for a desired action.
| Option | Action |
|---|---|
| **To rename __UniversalApplication__** | Navigate to **Global Objects** in the Project Explorer pane, right-click the **UniversalApplication** and select **Rename**.\[Omitted image "uac-rename-right-click.png"\] Alt text: From Global objects, right-click the UniversalApplication and select Rename. |
| **To change the name of the screen while configuring the screens and elements** | 1. Select the name of the application screen under the Screens and elements pane. The information of the selected application screen appears under the Properties pane. 2. Update the name of the application screen in the **Name** field and press **Enter**. The name of the application is updated in the Screens and elements pane. \[Omitted image "uac-update-screen-name.png"\] Alt text: Update the application screen name in the Properties section. |
| **To identify the screen uniquely** | Use the screen match rules to identify and locate the screen.During the execution, the plugin must identify the target screen uniquely to automate actions on the screen. Examples of attributes are the title or URL of the application screen. The attributes appear under the **Screen match rules** pane on the **Configure screens and elements** window. The UAC uses the screen match rules to identify the screen first, and uses the element match rule to identify the element, and then, perform actions on elements such as Click or Get Text. \[Omitted image "uac-connector-screen-match-rules.png"\] Alt text: Screen match rules. The image below shows an example of multiple elements that match the same criteria given in the Match Attributes section. A multiple number of instances, if any, appears when you refresh the captured element, is indicated within the brackets in red. In such cases, you must tweak the attributes to select exactly the element that needs to be automated. The user can refresh to check if the selected criteria match exactly one element. \[Omitted image "uac-connector-multiple-instances.png"\] Alt text: Multiple instances of captured element. |
| **To identify an element uniquely** | Use the element match rules to edit the values in the provided **Locator** and the **Match Attributes** sections.During the execution, the plugin must identify the target element uniquely to automate actions on the element. The attributes appear under the **Match Attributes** pane on the **Configure screens and elements** window. The UAC uses the screen match rules to identify the screen first, and uses the element match rule to identify the element, and then, perform actions on elements such as Click or Get Text. The image shows the match rules of an element captured. \[Omitted image "uac-connector-child-element-match-rules.png"\] Alt text: Element and its match rules. |
| **To find the elements on the application screen** | Use the locators of the captured elements.For more information, see [Find the elements on the application screen](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/find-elements-screen-uac.md). |
| **To view the path to an iframe, if any, in a captured element** | 1. In the **Screens and elements** pane, select the element. 2. Select the **Advanced** tab. The iframe appears. \[Omitted image "uac-connnector-iframe.png"\] Alt text: iframe appears. 3. From the **Locator** list, select a locator to find the path to the iframe. \[Omitted image "uac-connector-iframe-locator.png"\] Alt text: iframe locator. |