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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Use the GetRecordContextID component

# Use the GetRecordContextID component {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Get the Sys ID of the ServiceNow form record that is associated to an attended configuration with the GetRecordContextID component in the RPA Desktop Design Studio. Sys ID is the output of the component. For example, Sys ID is used to fetch the attachments in a record.

## 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. This is the output of your component. For more information, see [Assign bot process to an automation project](https://www.servicenow.com/docs/uHG42P5hp49nKDhIQ_pWiw "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/I0zUXsz4veyo~U40rWPMkA "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: none

## About this task

Use the GetRecordContextID component to fetch the Sys ID of the ServiceNow form record, from where the automation is triggered. Use the GetAttachmentsMetadata component to get the metadata of the attachments of this record. After getting the attachment Sys ID, use the DownloadAttachment component to download the attachment. For more information about these components, see [Use the DownloadAttachment component](https://www.servicenow.com/docs/ejHXP8vUHFazu7AoC2b6kQ "Download the attachments from the ServiceNow table record to the local drive by using the DownloadAttachment component in the RPA Desktop Design Studio.") and [Use the GetAttachmentsMetadata component](https://www.servicenow.com/docs/MQILpbM83D50MR7QibUKTQ "Get the metadata of all attachments that are associated with a ServiceNow table record by using the GetAttachmentsMetadata component in the RPA Desktop Design Studio.").

If you are triggering the automation from the ServiceNow form's UI action (button) and it executes using the Attended Robot application, then the GetRecordContextID component returns the Sys ID of the ServiceNow form record.

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

## Procedure

1. In the Toolbox pane, navigate to ServiceNowForms.
2. Drag the GetRecordContextID component to the Design surface.
3. Connect the data and control ports of the GetRecordContextID component to the corresponding ports of other components as described in the following table.  
   {#use-get-record-context-id-forms__table_jnw_jn1_krb__entry__3}

   | Port Name | Purpose of connection | Mandatory? |
   |-|-|-|
   | SysID \[Data Out\] | Returns the Sys ID of the ServiceNow form record. | No |
   | Control In | Connect to the Control Out port of one or more components. | Yes |
   | Control Out | Connect to the Control In port of another component or activity as per the required automation logic. | No |
   [ ]

   {#use-get-record-context-id-forms__table_jnw_jn1_krb}
4. **Optional:** To test the component, right-click the title bar of the component and select Run From Here.
{#use-get-record-context-id-forms__steps_p5h_g4n_11c}

*[\>]: and then