---
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 input form actions

# Configure input form actions in an input form screen {#ariaid-title1}

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

Add a button next to input form fields to give users the ability to perform various input actions. These actions include adding a comment, adding one or more attachments, and navigating to other screens.

## Before you begin

Role required: admin

This topic describes how to configure input actions for your various input fields. These configurations should be performed within the general setup of input form screens. Additional input action configurations are only
available when <kbd class="ph userinput">Screen</kbd> is selected in the Presentation style field of the Input form screen. For more information, 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.").

## About this task

Add a more menu button ![More menu icon.]() by specified input value fields.  
Note:  
The button appearance may vary between iOS and Android operating systems. The button is indicated with three dots either horizontally or vertically.

## 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're 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 either select an existing input form screen or New.  
   If you select New, select the Input form option in the Create a screen page, and then select Continue.
4. In the Input form screen page, select <kbd class="ph userinput">Screen</kbd> in the Presentation style field.
5. Select New in the Actions area to open the Input form action page.
6. Complete the following fields as needed.  
   {#input-actions-configure__table_lqq_zxv_21c__entry__2}

   | Field | Value |
   |-|-|
   | Properties ||
   | Name | Name of the action. |
   | Label | Label that displays for the action. |
   | Active | Whether the action is active. Inactive actions don't appear on the input form screen. |
   | Available offline | Determine whether this action is available offline. |
   | Input type | Option to choose if your input is populated from another source or modified by an action. Note: For this configuration select Input action. Apply input actions to an input field such as comments, attachments, or navigation functions. |
   | Icon | Icon used to represent your action on the user's mobile screen. |
   | Action Placement ||
   | Input form screen | Select the input form screen where the action appears. |
   | Input form section | Select the input form section where the action appears. If the selected input form screen doesn't contain sections, this field isn't available. |
   | Parent table | The parent table that the action applies to. This field is auto-filled. |
   | Parent input | Select which input the action will be applied to. |
   | Action attributes | Determine where or how the action handles the generated data. Note: Unless otherwise stated, all the listed attributes are available when you select Input actions in the Input type field. InputActionType: Input actions are actions that can be triggered in the more menu icon ![More menu icon.]() displayed by the side of an input value field. The actions are: <kbd class="ph userinput">attachments</kbd>, <kbd class="ph userinput">comment</kbd>, or <kbd class="ph userinput">button</kbd> (navigation function). ButtonId: The navigation function associated with the input action. This navigation input action can be either a <kbd class="ph userinput">global</kbd> or <kbd class="ph userinput">record</kbd> context. The <var class="keyword varname">ButtonId</var> is the sys_id of a record from the Button \[sys_sg_button\] table. HiddenAttachmentSources: Ability to prevent the upload of specific attachment sources from the user. The user can upload only images either from the phone's camera or the gallery. DataSourceID: The data source used for loading data from the database. Used for comment and attachment input action. Note: An <var class="keyword varname">ElementIdentifier</var> attribute is also required. For more information, see [Data sources](https://servicenow-prod.fluidtopics.net/fNNHkiliy1Xa~VIW4ExdMg "A data source is a loading mechanism that maps UI elements to specific database fields using element identifiers. Use data sources to retrieve and display data onto input form screens."). ElementIdentifier: The unique ID contained within a data source, used for loading data from the database. Used for comment and attachment input action. Note: A <var class="keyword varname">DataSourceID</var> attribute is also required. For more information, see [Data sources](https://servicenow-prod.fluidtopics.net/fNNHkiliy1Xa~VIW4ExdMg "A data source is a loading mechanism that maps UI elements to specific database fields using element identifiers. Use data sources to retrieve and display data onto input form screens."). UserActionID: A unique value that identifies this action record. It's needed to associate the action with a UI rule. Note: This field is available when the Input type field is <kbd class="ph userinput">Input source</kbd>. |
   [Table 1. Action fields]

   {#input-actions-configure__table_lqq_zxv_21c}
7. Enter a name for your input action in the Name field.
8. Enter a label for your input action that is visible to your users, in the Label field.
9. Select Input action in the Input type field.
10. Select where you want the action to show by completing the following fields in the Action placement area: Input form screen, Parent table, and Parent input.
11. Select New in the Action attributes area.  
    The input form action attributes opens.
12. Do the following for input actions that you want to include to the input field area.

    | Input action type | Procedure |
    | Attachment | 1. Select InputActionType in the Name field. 2. Enter the text <kbd class="ph userinput">attachments</kbd> in the Value field. 3. Select Save. {#input-actions-configure__ol_xjl_jxy_42c} |
    | Comment | 1. Select InputActionType in the Name field. 2. Enter the text <kbd class="ph userinput">comment</kbd> in the Value field. 3. Select Save. {#input-actions-configure__ol_jyw_sxy_42c} |
    | Navigation button | 1. Select InputActionType in the Name field. 2. Enter the text <kbd class="ph userinput">button</kbd> in the Value field. 3. Select Save. You're returned to the Input form action attribute table. 4. Select New in the Action attributes area. 5. Select ButtonId in the Name field. 6. Select a preconfigured navigation type in the Value field. For more information on creating navigation buttons, see [Navigation functions](https://servicenow-prod.fluidtopics.net/I6nV6wIRGzWO9nGAy0MFgA "Navigation functions transition users from their current screen to another screen or launcher screen."). Note: If the navigation function you selected has a Record context (as opposed to a Global context), you must map it to the specific record using data sources. If the <var class="keyword varname">ButtonId</var> refers to a button with a record context, it defaults to the context of the input form. However, you can override this default context by using the data source to link to a different record context. 7. Select Save. {#input-actions-configure__ol_yvy_vxy_42c} |
    |-|-|

    {#input-actions-configure__choicetable_p4n_gxy_42c}
13. Select Save.
{#input-actions-configure__steps_x4s_2wy_r2c}

## What to do next

To open the input form screen with attachments and comments already loaded from the instance \[instance\] table, you must configure the attributes <var class="keyword varname">DataSourceId</var> and <var class="keyword varname">ElementIdentifier</var>. For
example, in a scenario where multiple users work on the same form, the data source loading mechanism validates that the latest data is displayed to the next user on the input form screen. For a navigation function with a
record context, the record context is defined in the data source script. The script maps to the sys_id of the record that contains a context for the navigation. For more information, see [Configure data sources](https://servicenow-prod.fluidtopics.net/PTsq9~Z4qPpsQBZVHt~pwA "Configure data sources to map UI elements to specific database fields using element identifiers, enabling the retrieval and display of data on input form screens. This mapping verifies that each UI element accurately reflects the corresponding data field within a record.").

*[\>]: and then