---
sourceDocument: Australia Mobile Configuration and Navigation
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/mobile

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - Development, Data and Analytics


---

# Write-backs

# Write-backs {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The following describes how data is written back from ServiceNow
mobile apps.

## Updating fields {#sg-mobile-securitywrite-backs__section_dx4_bm5_ddb}

When a user updates a field in a mobile app, the following steps occur.

1. The mobile app sends the Token and the action metadata, for example the ID, or the field to be updated, to the instance.
2. The instance directs the action based on the relevant API.
3. The instance completes the action and sends a response to the mobile app.
4. Based on the response, the mobile app reflects the field changes and action availability in the UI.
{#sg-mobile-securitywrite-backs__ol_ocj_ct5_ddb}

## Attaching documents {#sg-mobile-securitywrite-backs__section_p3l_qt5_ddb}

When attaching documents, the following steps occur.

1. The mobile app asks the user to attach a document, for example, an image.
2. The mobile app sends the document and Token to the instance.
3. The instance places the document based on the relevant API.
4. The instance sends a response back to the mobile app.
{#sg-mobile-securitywrite-backs__ol_jrf_st5_ddb}