{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":22295,"path":"integrate-applications/use-attended-configurations-forms.md","title":"Use the AttendedConfigurations component","bundle":null,"doc_type":null,"release":"australia","body":"\n# Use the AttendedConfigurations component\n\nWhen 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.\n\n## Before you begin\n\nIf 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/assign-bot-process.md).\n\nEnsure you are familiar with Embedded Task Automation concepts. For more information, see [Embedded Task Automation \\(ETA\\) in RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/embedded-task-auto-rpa.md).\n\nRole required:\n\n-   sn\\_rpa\\_fdn.rpa\\_developer or sn\\_rpa\\_fdn.rpa\\_admin, if you are running the automation from RPA Desktop Design Studio\n-   sn\\_rpa\\_fdn.rpa\\_assisted\\_user, if you are running the automation from the Attended Robot application.\n\n## About this task\n\nThe AttendedConfigurations component segregates the execution of the automations in a single automation project and calls the respective logic according to the action invoked.\n\nIf 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.\n\nYou can configure the properties for the AttendedConfigurations component. For more information about these properties, see [Properties of the Forms components](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/sn-forms-properties.md).\n\nFor 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.\n\nLet'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.\n\n## Procedure\n\n1.  In the Toolbox pane, navigate to **ServiceNow** > **Forms**.\n\n2.  Drag the AttendedConfigurations component to the Design surface.\n\n3.  Click the component settings icon \\(\\[Omitted image \"component-settings-icon.png\"\\] Alt text: Component settings icon.\\).\n\n4.  Select one or more applicable attended configurations.\n\n    In this example, select both the attended configurations \\(Get Prices and Update Price\\).\n\n    \\[Omitted image \"attended-config-forms-studio.png\"\\] Alt text: Select attended configurations.\n\n5.  Click **OK**.\n\n    You will view more than one control out port.\n\n6.  Connect the data and control ports of the AttendedConfigurations component to the corresponding ports of other components as described in the following table.\n\n    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.\n\n    |Port type|Purpose of connection|Mandatory?|\n    |---------|---------------------|----------|\n    |Control In|Connect to the Control Out port of one or more components.|Yes|\n    |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|\n\n7.  To test the component, right-click the title bar of the component and select **Run From Here**.\n\n\n**Parent Topic:**[Forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/forms_sn_rpa_studio.md)\n\n"}}