---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Use the AttendedConfigurations component

# Use the AttendedConfigurations component {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
When you use the AttendedConfigurations component, it shows a list of attended configurations associated to the selected same bot process. To select and give control out port for each configuration that routes the automation
logic.

## Before you begin

If you are running an automation from RPA Desktop Design Studio, then assign the automation to the bot process by using the Assign bot process option from the Design tab of RPA Desktop Design Studio. In the Bot Process field, ensure to select an attended bot process that is enabled with Embedded Task Automation. In the Attended Config
field, ensure to select an associated attended configuration. In the Record Context field, ensure to enter the Sys ID or URL of the ServiceNow form record. For more information, see [Assign bot process to an automation project](https://www.servicenow.com/docs/oUXPBvfYND_4jqTOwRNn~Q "Assign a bot process to an automation project in RPA Desktop Design Studio to start using the bot process resources.").

Ensure you are familiar with Embedded Task Automation concepts. For more information, see [Embedded Task Automation (ETA) in RPA Hub](https://www.servicenow.com/docs/eF6bSd361W_d5xgrlFaVIg "With the embedded task automation feature, trigger attended bot processes (attended automations) from the ServiceNow forms, apart from initiating them from the Attended Robot application.").  
Role required:

* sn_rpa_fdn.rpa_developer or sn_rpa_fdn.rpa_admin, if you are running the automation from RPA Desktop Design Studio
* sn_rpa_fdn.rpa_assisted_user, if you are running the automation from the Attended Robot application.
{#use-attended-configurations-forms__ul_ctw_yfd_b1c}

## About this task

The AttendedConfigurations component segregates the execution of the automations in a single automation project and calls the respective logic according to the action invoked.

If you are triggering the automation from the ServiceNow form's UI action (button) and it executes using the Attended Robot application, then the AttendedConfigurations component routes the automation flow from the associated attended configuration.

You can configure the properties for the AttendedConfigurations component. For more information about these properties, see [Properties of the Forms components](https://www.servicenow.com/docs/fWQ2keL2Uw7TsfFI6lRc~Q "Learn about the properties of the Forms components in RPA Desktop Design Studio.").

For example, if an automation requires two UI actions, create two attended configurations in RPA Hub, that are associated to the same bot process and table. Define the automation logics separately for these UI actions, under different activities.

Let's consider a currency price retrieval use case, where one automation is built with two automation logics for UI actions such as Get Prices and Update Price. These UI actions are associated to two attended configurations,
Get Prices and Update Price. The attended configurations are associated to the same bot process and table. The following steps provide guidance of how to use the AttendedConfigurations component in this use case.

## Procedure

1. In the Toolbox pane, navigate to ServiceNowForms.
2. Drag the AttendedConfigurations component to the Design surface.
3. Click the component settings icon (![Component settings icon.]()).
4. Select one or more applicable attended configurations.  
   In this example, select both the attended configurations (Get Prices and Update Price).
   Figure 1. Example: Select attended configurations
5. Click OK.  
   You will view more than one control out port.
6. Connect the data and control ports of the AttendedConfigurations component to the corresponding ports of other components as described in the following table.  
   In this example, map the Get Prices Control Out port to the corresponding activity. Similarly, map the Update Price Control Out port to the corresponding activity. After you select the Get Prices UI action, the
   corresponding logic is executed. Similarly, after you select the Update Price UI action, the corresponding logic is executed.
   {#use-attended-configurations-forms__table_jnw_jn1_krb__entry__3}

   | Port type | Purpose of connection | Mandatory? |
   |-|-|-|
   | Control In | Connect to the Control Out port of one or more components. | Yes |
   | Control Out | \[Multiple\] For each selected attended configuration, a control out is created. Connect to the Control In port of another component or activity as per the required automation logic. | No |
   [ ]

   {#use-attended-configurations-forms__table_jnw_jn1_krb}
7. **Optional:** To test the component, right-click the title bar of the component and select Run From Here.
{#use-attended-configurations-forms__steps_p5h_g4n_11c}

*[\>]: and then