---
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 screens with signature inputs

# Configure input form screens with signature inputs {#ariaid-title1}

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

Configure input fields that your users can use to sign electronically on the input
form screen. Users can sign on the screen or type their name to record their
signature.

## Before you begin

You must create an input form screen before you create inputs. 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

## About this task

Signature inputs support both declarative and scripted writeback actions in action
items. For information about action items, 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.").

Configure these inputs by using the signature input type with the optional
IsOverlay attribute. By default, signatures are rendered in
the full modal window. If you set the IsOverlay attribute to
<kbd class="ph userinput">true</kbd>, the signature renders in a half modal window. When
a signature input is configured as the only input on a page and the
IsOverlay attribute is set to <kbd class="ph userinput">true</kbd>,
the attribute is ignored. In this case, the signature is rendered in the full modal
window.  
Important:  
For HR workflows that use a precondition for an HR Task Signature, these preconditions must be replaced with the new signature input type. Don't configure both the precondition as an HR Task Signature and the signature input type. Using both is a misconfiguration.

Signature inputs are available [offline](https://servicenow-prod.fluidtopics.net/0aYMnDp0VjYheVygRWNJuw "Configure offline mode to enable your users who have no internet connection to continue working from a mobile device."). [Mobile UI
rules](https://servicenow-prod.fluidtopics.net/w0HeqUgAog6EWlo9Jw6wRA "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.") apply to signature inputs.

## Procedure

1. Navigate to All and enter <kbd class="ph userinput">sys_sg_parameter_screen_list.do</kbd> in the filter.
2. Select the input form screen to which you want to add the signature input.
3. Select the Inputs tab.
4. Double-click the Insert a new row... and enter the following information for your signature input as needed.  
   {#configure-signature-inputs__table_wj4_r3p_tvb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the input |
   | Label | Label that displays for the input |
   | Input Type | The type of input. Select Signature. |
   | Placeholder | Text that appears in an input field before the user enters a value. |
   | Page | Input form screen page on which the signature input appears. |
   | Order | Order in which the signature input appears in the input form screen. |
   | Mandatory | Option to mark the signature input as required. |
   | Readonly | Option to mark the signature input as read-only. |
   | Auto-fill Variable | The auto-fill variable used for this signature input. |
   [Table 1. Inputs form]

   {#configure-signature-inputs__table_wj4_r3p_tvb}
5. Right-click the Input form screen banner and select Save to save the signature input and stay on the form.
6. **Optional:** If you want to configure the IsOverlay attribute to open the signature in a half modal window, double-click the Name of the signature input you just created to configure the attribute.
   1. Scroll down to the Attributes section of the form and then double-click Insert a new row....
   2. In the Name field, enter <kbd class="ph userinput">IsOverlay</kbd> and select the check mark to save the attribute name.
   3. Double-click the Value field and enter <kbd class="ph userinput">true</kbd> to configure the signature to open in a half modal window.

   {#configure-signature-inputs__substeps_xtq_25l_zvb}  
   If you want the signature to open in a full modal window, don't configure the IsOverlay attribute. By default signature inputs open in a full modal window.
7. When you finish configuring all the fields you want, select Update.

## What to do next

If you want to configure a scripted writeback action to save the signature input for
this input form screen, add the scripted writeback action to the action item. For
details, see [Configure a scripted writeback action that saves a signature input](https://servicenow-prod.fluidtopics.net/FJTQEEmI8hXSd3pFBP_Peg "Configure an action item's scripted writeback action that can save the signature input in your input form screen.").