---
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


---

# Configure attributes for input form screen variables

# Configure attributes for input form screen variables {#ariaid-title1}

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

Use screen variables to collect information from the user automatically or define default information. Variables can
include information like user IDs and GPS coordinates.

## Before you begin

You must create an input form screen before you create variables and attributes. For
information about creating an input form screen, see [Configure an input form screen](https://servicenow-prod.fluidtopics.net/PVSI3Faa8_DKNk1SxKRsJQ "Configure an input parameter so that your users can see a list of records from their mobile app. To access a record from the list, a user just has to tap the record name.").

Role required: admin

## Procedure

1. Navigate to AllSystem MobileMobile App Builder.  
   The Mobile App Builder opens in a new browser tab and displays the application scope selection screen.
2. Search for the application scope you are working in and then select the name of the application scope.  
   The Mobile App Builder categories home screen displays.
3. Select the Screens category and then select the input form screen for which you want to configure variables.
4. Scroll down to the Variables section of the form, and select New to create a variable.  
   The Variable form appears.
5. Complete the following fields as needed.  
   {#param-screen-config-variables__table_um3_qx5_2tb__entry__2}

   | Field | Description |
   |-|-|
   | Name | The name of your variable |
   | Variable type ||
   | Database field | Data from a field. This field uses the FieldName attribute. After configuring the Variable placement section, see Step 6 to configure the attribute. |
   | Date | Current date. This variable does not take an attribute. After configuring the Variable placement section, see Step 8 to finish the variable configuration. |
   | Constant | A static value set by the administrator using the ConstantValue attribute. After configuring the Variable placement section, see Step 6 to configure the attribute. |
   | GPS Coordinates | Longitude and latitude of the user. This variable does not take an attribute. After configuring the Variable placement section, see Step 8 to finish the variable configuration. |
   | Offline Mode | Input is available when the mobile app is offline. This variable does not take an attribute. After configuring the Variable placement section, see Step 8 to finish the variable configuration. |
   | User | Sys_id of the user. This variable does not take an attribute. After configuring the Variable placement section, see Step 8 to finish the variable configuration. |
   | ParentContext | Context information that is carried from a parent record into an action. Uses the ContextField attribute. After configuring Variable placement, see Step 7 to configure the variable and attribute. |
   | Scripted | Script that auto-fills inputs. Uses the Script attribute. After configuring the Variable placement section, see Step 7 to configure the variable and attribute. |
   | Variable placement ||
   | Input form screen | Select the input form screen where the variable appears. |
   | Input form section | Select the input form section where the variable appears. If the input form screen does not contain sections, this field is not available. |
   [Table 1. Variable fields]

   {#param-screen-config-variables__table_um3_qx5_2tb}
6. **Optional:** If you selected Database field or Constant as your variable type, the Variable attributes section appears.  
   In the Variable attributes section, select New to configure the variable attribute. Depending on the variable type you set in Step 5, select the attribute properties.{#param-screen-config-variables__table_if5_ppt_gtb__entry__2}

   | Attribute name | Properties |
   |-|-|
   | FieldName | Set the following information: * Table: The table you want to use. * Value: The name of the field in that table. {#param-screen-config-variables__ul_e4b_spt_gtb} Use this attribute if you have selected the Database field variable type. See Step 8 to finish the variable configuration. |
   | ConstantValue | Enter the static data defined by the administrator. Use this attribute if you have selected the Constant variable type. See Step 8 to finish the variable configuration. |
   [Table 2. Attribute properties]

   {#param-screen-config-variables__table_if5_ppt_gtb}
7. **Optional:** If you want to configure ParentContext or Scripted variable types, then do the following:
   1. Save the input form screen by selecting Save.
   2. Navigate back to the input form screen node in the left navigation menu.
   3. On the input form screen form, select the options menu icon ![Options menu icon.]() in the upper right corner of the form in Mobile App Builder, and select Open in platform.
   4. Select the Variables tab.
   5. Under Name, select the name you entered for the variable in Step 5.
   6. Select one of the following Variable Types.  
      {#param-screen-config-variables__table_b3w_kvv_qtb__entry__2}

      | Variable Type | Description |
      |-|-|
      | ParentContext | Context information that is carried from a parent record into an action. This type uses the ContextField attribute. For example, use this variable when an employee goes out on a service call and they must log associated expenses like mileage. |
      | Scripted | Script that auto-fills inputs. This type uses the Script attribute. For example, you can pre-fill a building number based on an end user's profile when making a reservation. |
      [ ]

      {#param-screen-config-variables__table_b3w_kvv_qtb}
   7. In the Attributes section under Name, double-click Insert a new row... and enter the name of your variable attribute as listed in the following table.  
      Important:  
      Enter the Attribute Name exactly as it is listed in the table. The name is case-sensitive.
      {#param-screen-config-variables__table_zlh_nwv_qtb__entry__2}

      | Attribute Name | Description |
      |-|-|
      | ContextField | Enter this attribute name for ParentContext variables. Note: Enter the attribute name exactly. It is case-sensitive. |
      | Script | Enter this attribute name for Scripted variables. Note: Enter the attribute name exactly. It is case-sensitive. |
      [ ]

      {#param-screen-config-variables__table_zlh_nwv_qtb}
   8. After entering the attribute name, select the check (![Check icon.]()) to save the attribute.
   9. Double-click the field under Value and add the appropriate value for the attribute you are configuring as described in the following table.  
      {#param-screen-config-variables__table_ikp_3xv_qtb__entry__2}

      | Attribute Name | Description |
      |-|-|
      | ContextField | Enter the field name from the parent screen whose contents you want to populate the input form screen field. |
      | Script | Paste the JavaScript code that auto-fills the input form screen field. For example, you can pre-fill a building number based on an end user's profile when making a reservation. |
      [ ]

      {#param-screen-config-variables__table_ikp_3xv_qtb}
   10. Select the check icon (![Check icon.]()) to save attribute.
   11. Select Update.
   12. Navigate back to Mobile App Builder by selecting that browser tab.
   {#param-screen-config-variables__substeps_h3v_ltv_qtb}
8. In Mobile App Builder, select Save.  
   Important:  
   If you performed optional Step 7, you already saved the record in Mobile App Builder so you don't need to save it again.

## What to do next

After you have created your input form screen variables, you can map these variables
to input form screen inputs or action items. For details on this process, see [Configure an action item](https://servicenow-prod.fluidtopics.net/yoKrBS4snk1zej1cWalP~A "For an action function to work, you must create an action item to associate with the action function. Action items define what the action function is and how it works.").

*[\>]: and then