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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - evelopment, Data and Analytics


---

# Configure auto-fill inputs on input form screens

# Configure auto-fill inputs on input form screens {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Streamline form completion on input form screens by configuring auto-filled inputs based on one or more user inputs. Auto-fill inputs are configured by using mobile client scripts.

## Before you begin

Role required: admin

## About this task

Auto-fill inputs are configured by using mobile client scripts that run as a UI rule action in the UI rule of an input form screen. These scripts run in UI rules with an OnChange trigger type. For more
information about UI rules and UI rule actions, see [Mobile UI Rules](https://www.servicenow.com/docs/r~w4JPN12qjPAnE4vGN~mw "Use Mobile UI rules to build rules that modify the mobile UI. These modifications can include hiding and displaying fields, making fields mandatory, performing field value calculations, and applying UI styles to different UI elements.").  
Note:  
* Auto-fill inputs are not supported in offline mode.
* Only one Run client script UI rule action can be configured for each mobile UI rule.
* Input form screens were formerly called parameter screens. However, the name Parameter Screen is still used in the Mobile UI Rule form.
{#config-autofil-inputs-nptfrmscrn__ul_s2w_wlb_hbc}

## Procedure

1. Navigate to AllSystem MobileMobile UIMobile UI Rules.
2. In the Mobile UI Rules list, either select New to create a new mobile UI rule or select an existing mobile UI rule to configure it for auto-fill inputs.  
   Important:  
   If you select an existing mobile UI rule, make sure it has the following characteristics:
   * Parent Table is set to Parameter Screen.
   * At least one of the Triggers is OnChange.
   {#config-autofil-inputs-nptfrmscrn__ul_dlg_lmb_hbc}
3. Configure a mobile UI rule for auto-fill inputs on input form screens by completing one of the following options.  

   If you selected New in Step 2:
   :
       1. In the Mobile UI Rule form, fill in the fields as follows:

          {#config-autofil-inputs-nptfrmscrn__table_krx_jvf_3bc__entry__2}

          | Field | Value |
          |-|-|
          | Name | Name of the mobile UI rule. |
          | Active | Whether the mobile UI rule is active. |
          | Condition | Condition under which the mobile UI rule is used. If the Condition field is left empty, this UI rule runs whenever any input changes. For example, to trigger this UI rule when a particular input changes, use the VALCHANGES operator. Entering <kbd class="ph userinput">urgencyVALCHANGES</kbd> in the Condition field causes the UI rule to be triggered only when the value of an input named urgency changes. For details on the operators available for your condition, see [Operators available for filters and queries](https://www.servicenow.com/docs/access?context=r_OpAvailableFiltersQueries&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US). |
          | Parent Table | The parent table that the mobile UI rule applies to. Select Parameter Screen. |
          | Parent | The input form screen to which your mobile UI rule is applied. |
          | Triggers | Select onChange. |
          | User Action Id | A unique value that identifies this action record. It's needed to associate the action with a UI rule. Important: This option doesn't apply to configuring auto-fill inputs on input form screens. Don't set a value for this field. |
          | Order | Order in which the mobile UI rule runs. Important: This option doesn't apply to configuring auto-fill inputs on input form screens. Don't set a value for this field. |
          | Reverse If False | When this field is selected, the mobile UI rule actions are reversed if the condition evaluates as false. Important: UI rule actions that use the Run Client Script operation can't run if the condition evaluates to false. Don't select this check box. |
          [ ]

          {#config-autofil-inputs-nptfrmscrn__table_krx_jvf_3bc}
       2. Select Submit.
       {#config-autofil-inputs-nptfrmscrn__ol_b52_2vf_3bc}

   If you selected an existing mobile UI rule to configure it for auto-fill inputs in Step 2:
   :
       1. In the Mobile UI Rule form, fill in the fields as follows:

          {#config-autofil-inputs-nptfrmscrn__table_egk_dxf_3bc__entry__2}

          | Field | Value |
          |-|-|
          | Condition | Condition under which the mobile UI rule is used. If the Condition field is left empty, this UI rule runs whenever any input changes. For example, to trigger this UI rule when a particular input changes, use the VALCHANGES operator. Entering <kbd class="ph userinput">urgencyVALCHANGES</kbd> in the Condition field causes the UI rule to be triggered only when the value of an input named urgency changes. For details on the operators available for your condition, see [Operators available for filters and queries](https://www.servicenow.com/docs/access?context=r_OpAvailableFiltersQueries&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US). |
          | Parent Table | Make sure this field is set to Parameter Screen. |
          | Triggers | Make sure that at least one of the Triggers is set to onChange. |
          [ ]

          {#config-autofil-inputs-nptfrmscrn__table_egk_dxf_3bc}
       2. Select and hold (or right-click) the banner and select Save.
       {#config-autofil-inputs-nptfrmscrn__ol_mt5_wwf_3bc}
4. Navigate to the mobile UI rule that you configured in Step 3 to configure the mobile UI rule action for auto-fill inputs on your input form screen.
5. In the Mobile UI Rule Actions section of the mobile UI rule form, select New.  
   The Mobile UI Rule Action form appears.
6. In the Mobile UI Rule Action form Operation field, search for and select Run Client Script.  
7. Write the client script in the Client script field.  
   Client scripts use the m_form object and the MobileScriptIncludeCaller class. For details on these JavaScript APIs, see [MobileScriptIncludeCaller - Client](https://www.servicenow.com/docs/access?context=MobileScriptInclCallerClientAPI&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) and [m_form - Client](https://www.servicenow.com/docs/access?context=m_formClientAPI&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) in the API reference documentation.  
   When writing the client script, be aware of the following points:
   * Don't change the signature of the onChange function.
   * The argument inputName is a string that is the name of the input whose value changed.
   * The argument newValue contains the new value of that input after the change.
   {#config-autofil-inputs-nptfrmscrn__ul_fm3_myb_hbc}
8. Select Submit.

*[\>]: and then