---
sourceDocument: Brazil Mobile Configuration and Navigation
sourceDocumentLink: https://www.servicenow.com/docs/r/mobile

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - Development, Data and Analytics


---

# Write-back action support

# Write-back action support {#ariaid-title1}

Release version: Brazil  
Updated November 2, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Mobile scripting can use write-back actions and write-back-action steps, so data from multiple tables can be manipulated while offline and online.
Before the Brazil version, offline logic could only be written within a write-back action step. From the Brazil version, you can also write offline logic as a mobile script in a write-back action that runs both on offline and online.

For write-back action configuration information, see [Configure action items and action steps in offline mode](https://www.servicenow.com/docs/b4EUuym8ZNli09E9R_CaYg "Configure action items to execute actions like create, edit and delete records while in offline mode. For an action item to perform multiple processes you must define separate action steps.").
Consider the following offline and online considerations when using navigation commands in the ServiceNow AI Platform:

Write-back actions
:   When using the navigation command sys_sg_write_back_action_item.list it opens the Action items table. When you select Script in the Type field, the script text box opens. Add
    your mobile script syntax which runs both online and offline.

Write-back action steps
:   When using the navigation command sys_sg_write_back_action_step.list it opens the Action steps table. In this record a Writeback action item must be selected as it associated with its parent item. When you select
    Script in the Type field, you must also choose a value in the Applicable for field, either Online, Offline, or Both. Your choice determines which syntax to use:

    * Online: Use regular script syntax, which supports broader GlideRecord capabilities.
    * Offline: Use mobile script syntax only, as it is the only syntax that supports offline.
    * Both: Use mobile script syntax only, because other scripts can't mix mobile and non-mobile syntax.
    {#wba-mobile-script__ul_iqz_gpq_clc}