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


---

# Input form screen attributes for inputs

# Input form screen attributes for inputs {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 14 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Input form screen attributes for inputs

This guide details the configuration of various input types within ServiceNow input form screens, enabling you to customize input appearance and behavior.
Attributes are case-sensitive and allow you to set parameters such as input formats, value limits, and data sources to optimize user interaction and data collection on mobile and web forms.
Show full answer Show less  

## General Attributes

* **DescriptionRenderType:** Allows HTML formatting in input descriptions.
* **DataSourceId and ElementIdentifier:** Link inputs to data sources for loading values (not supported for signature inputs).

## Attachment Inputs

Enable file attachments in scripted action forms requiring scripted action items and an `actionResult` object to upload files. You can restrict attachment origins to camera, files, or gallery sources using the **HiddenAttachmentSources** attribute to control where users can source images.

## Barcode Inputs

Support single or multi-barcode scanning via mobile app. Configure multi-scan behavior with **MaxEntries** to define maximum scans per session. Grouped scans require a dedicated barcode section with a section-level **MaxEntries** attribute.

## Boolean Inputs

Allow true/false inputs rendered as checkboxes or toggle switches via the **RenderType** attribute.

## Choice Inputs

* **MultiSelect:** Enables multiple selections.
* **Table and Field:** Use existing tables and fields to populate choices.
* **Inline:** Displays choices on the same screen or navigates to a separate screen.
* **InlineMaxItems:** Controls how many choice chips are displayed before showing a "See all" button.
* **RenderType:** Options include rendering choices as images.
* **EnableSearch and SearchPlaceholder:** Add a search bar with customizable placeholder text.
* **SearchType:** Defines search behavior with options "startswith" or "contains".

## Custom Map Inputs

Link indoor maps for resource reservations with attributes specifying map configuration, provider, floor, and sorting/filtering through a single **ScreenId** attribute. Only one custom map attribute should be used per input.

## Date/Time Inputs

* **RenderType:** Choose between date only or date-time display.
* **IncludeTimezone:** Optionally include mobile device timezone data.
* **MaxRangeDays, MinRangeDays, MaxRangeHours, MinRangeHours:** Configure allowable date/time range limits to restrict past or future selections.

## Number Inputs

* **CustomErrorMessage:** Define custom validation error messages.
* **Max and Min:** Set numeric input boundaries.
* **RenderType:** Display as percentage, line, box, or integer-only input (disallows decimals).
* **SkipValidationWhenHidden:** Option to skip validation for hidden inputs.

## Ranking Inputs

Enable drag-and-drop sorting of manually defined choices. Only general attributes are applicable.

## Reference Inputs

* Require **SourceTable** , **SourceFieldName** , and **TargetTable** to link input to reference fields on your instance.
* Optional attributes include **MultiSelect** , **MobileViewId** , **EnableSearch** , **SearchPlaceholder** , **Conditions** (encoded queries), and **SearchType** to refine search behavior.

This enables users to select related records efficiently, e.g., assigning users to incidents.

## Signature Inputs

Capture e-signatures with optional **IsOverlay** attribute to toggle between full and half modal windows for signature capture. Note that signature inputs do not support data source attributes.

## String Inputs

* **Inline:** Choose inline editing or modal dialog.
* **MaxLength:** Limit maximum character count.
* **ShowDeleteAll:** Display a delete button when text exists.
* **ConfirmDeletion:** Require confirmation before deleting text.

## Screen Inputs

Transform list screens into selectable lists to allow multiple item selection and write-back operations. Configure with **ScreenId** for the list screen and **GetDataFromParent** to inherit filters from parent screens.  
Different types of inputs are available for use in input form screens, and you can use different attributes to configure the inputs.
Use input attributes to define the appearance and set limitations on your inputs. Examples include setting minimum and maximum values, or displaying an input value as a percentage.  
Note:  
All attributes are case-sensitive.

## General attribute {#parameter-screen-var-attr__section_r1p_pcy_2qb}

You can use this attribute with any input form screen, regardless of the input type.
{#parameter-screen-var-attr__table_s1p_pcy_2qb__entry__2}

| Attribute | Description |
|-|-|
| DescriptionRenderType | Define a render type for the input description. html: Enables you to use HTML tags to format the text in the Description field of your input. |
| DataSourceId | Define this attribute whenever you create a data source mechanism to load input values. For more information, see [Data sources](https://www.servicenow.com/docs/i0BdIiGlSyp_8sPhSsmF4Q "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."). Note: This attribute is not supported with signature inputs. |
| ElementIdentifier | Define this attribute whenever you create a data source mechanism to load input values. For more information, see [Data sources](https://www.servicenow.com/docs/i0BdIiGlSyp_8sPhSsmF4Q "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."). Note: This attribute is not supported with signature inputs. |
[ ]

{#parameter-screen-var-attr__table_s1p_pcy_2qb}

## Attachment inputs {#parameter-screen-var-attr__section_txr_k1x_b4b}

|-|-|
| Use attachment inputs to enable users to attach files in an input form screen. Attachment inputs require a scripted action item and an actionResult object to upload a file. Note: Attachment inputs are only supported for scripted actions. | ![Attachment input example.]() |
[ ]

{#parameter-screen-var-attr__table_uxr_k1x_b4b}  
The following is an example of code that contains attachment inputs.

    (function WriteBackAction(parm_input, parm_variable, actionResult) {

      //other write-back inputs and variables here

        actionResult.addAttachment("attach", "incident", gr.getUniqueValue()); //where "attach" is the input name from above screenshot, and "incident" is the table name

    })(parm_input, parm_variable, actionResult); 

Restrict attachment sources to users
:   You have the option to limit the origins of attachments, to ensure that images are sourced from one or all of the following:

    * on-site via a camera
    * from the user's phone gallery
    * from the user's file system

    {#parameter-screen-var-attr__ul_w4l_g2v_12c}

    In the Input attribute record, select <kbd class="ph userinput">HiddenAttachmentSources</kbd>. Select either <kbd class="ph userinput">camera</kbd>, <kbd class="ph userinput">files</kbd> or <kbd class="ph userinput">gallery</kbd>, from the
    Value field and then select Save. Repeat the process if you want to include more than one attachment source. For more information, see [Define attachment sources available to users](https://www.servicenow.com/docs/BU6o~DZVg~0eowMOp7hVAg "Control the origin of where images and files are sourced from, including a phone's gallery, camera, or file system. This capability confirms that images can’t be reused and verifies that they aren't AI-generated.").
    {#parameter-screen-var-attr__table_qyx_sfg_zdc__entry__2}

    | Attribute | Description |
    |-|-|
    | HiddenAttachmentSources | Decide where you don't want images sourced from. Select one of the following source values: <kbd class="ph userinput">camera</kbd>, <kbd class="ph userinput">files</kbd> or <kbd class="ph userinput">gallery</kbd>, from the Value field. Note: To avoid images and files being obtained from more than one source, add additional HiddenAttachmentSources attributes after you save the attribute you are currently configuring. |
    [ ]

    {#parameter-screen-var-attr__table_qyx_sfg_zdc}

## Barcode inputs {#parameter-screen-var-attr__section_qh2_zms_rvb}

Use barcode inputs to scan single or multiple barcodes. Barcodes are machine-readable codes in the form of numbers and a pattern of parallel lines of varying widths. These codes are used to identify items such as products,
parts, or assets. You can use this input type to enter information about items into your ServiceNow instance by using your mobile app.  
* Barcode inputs can be configured for single scans, multi-scans, or grouped scans. Single scans enable the user to scan only once. In this case, the user must rescan by tapping the scan icon, which clears the scan value. You don't need to configure an attribute for a single scan barcode input.
* Multi-scan inputs can be configured with the MaxEntries attribute. If your input form screen barcode input is configured with the MaxEntries attribute, users can quickly scan multiple barcodes sequentially without leaving the scanning interface.
* Grouped scans can be configured to scan multiple barcodes associated with an asset that must be grouped in a set. To configure a grouped barcode input, you must create a barcode section in the input form screen that has barcode inputs only. Then the section MaxEntries attribute must be configured for the grouped barcode section so that users can scan multiple groups of barcodes.
{#parameter-screen-var-attr__ul_yz5_mql_zvb}
Figure 1. Barcode scanning in a mobile app  
You can use this attribute with barcode inputs.{#parameter-screen-var-attr__table_dsm_44s_rvb__entry__2}

| Attribute | Description |
|-|-|
| MaxEntries | Used only for configuring multi-scanning and multiple groups of barcodes. Sets the maximum number of barcodes that a user can scan at a time. For example, you can set the value to <kbd class="ph userinput">5</kbd> to enable users to rescan 5 times. Note: Use this attribute for multi-scan barcode inputs only. If your barcode input is intended for single scans, no attribute is required. |
[ ]

{#parameter-screen-var-attr__table_dsm_44s_rvb}

For information about creating an input form screen with barcode inputs, see [Configure input form screens with single and multi-scan barcode inputs](https://www.servicenow.com/docs/XU1jIHIjTy7rd0feQoPY4w "Configure input fields that you can use to scan a single barcode one at a time or multiple barcodes without leaving the scanning interface.") and [Configure input form screens with grouped scan barcode inputs](https://www.servicenow.com/docs/w3vkRIoCJRYSEfypGEsyow "Configure input form screens that support grouped scans. Grouped scans enable you to scan multiple barcodes that are associated with assets that must be scanned in a set.").

## Boolean inputs {#parameter-screen-var-attr__section_t3b_1br_b4b}

|-|-|
| Use Boolean inputs for inputs with true or false values. You can configure Boolean inputs to appear either as a check box or as a toggle switch. | ![Examples of boolean inputs configured as a check box or toggle switch.]() |
[ ]

{#parameter-screen-var-attr__table_wdg_rmw_b4b}

You can use these attributes with Boolean inputs.
{#parameter-screen-var-attr__table_u3b_1br_b4b__entry__2}

| Attribute | Description |
|-|-|
| RenderType | Specify a render type for the Boolean input. Checkbox :   Displays the input as a check box. toggle :   Displays the input as a toggle. |
[ ]

{#parameter-screen-var-attr__table_u3b_1br_b4b}

## Choice inputs {#parameter-screen-var-attr__section_fdn_4br_b4b}

|-|-|
| Use choice inputs to give your users options to select from. You can create these choices manually or use an existing table and field to provide the choices. Configure a choice input to enable users to select a single choice, or multiple choices. The option to select more than one chip in a category is marked by a + sign on the chips. Define the number of chips to display, enabling the user to see all options available on a single input form screen. If the defined number of chips to display exceed the defined amount, a See all button is displayed. Tap on the See all button to open a page with all the options listed. | Figure 2. Single and multiple choice input options on an input form screen |
[ ]

{#parameter-screen-var-attr__table_ckj_vmw_b4b}

You can use these attributes with choice inputs.
{#parameter-screen-var-attr__table_gdn_4br_b4b__entry__2}

| Attribute | Description |
|-|-|
| MultiSelect | Option to enable users to select multiple choices for the input. The value must be true or false. Multi-select options are indicated with a "+" sign on the chip. |
| Table | The table where the choice field is located. Note: Use this option to use the choices in an existing table and field rather than manually creating choices. You must select a field on this table using the Field attribute. |
| Field | The field that contains your choices. Note: Use this option to use the choices in an existing table and field rather than manually creating choices. The field defined in this attribute must be on the table defined in the Table attribute. |
| Inline | Option to select how to display your choice inputs. By default, the value is false, meaning that the choice display is on the same screen, removing the need to navigate to a separate screen. For a visual example, see the image in the Choice inputs introduction. If you select true, a list-type option displays where users are required to navigate to an additional screen, after a selection is made. Figure 3. Inline choice list-style option showing the need for a secondary screen |
| InlineMaxItems | Option to define the number of chips to display within an input form screen section. The following inputs in the Value field are available: * Empty: Displays the default of up to 8 choice values. If there are more choices than 8 choice values, the See all button displays. * Negative numerical value: Displays all the choice values, even if it exceeds 8 values. * Positive numerical value: Displays the number of choice values defined. If there are more choices than the entered numerical value a See all button displays. {#parameter-screen-var-attr__ul_zps_t2h_zdc}The following image illustrates a scenario where 8 is the value entered and there are 12 choice values. The first screen displays 8 values. When the user taps the See all button, a new screen opens with all the 12 choice values displayed.Figure 4. Choice list with See all button |
| RenderType | Option to render the choice options as an image for the choice input. The value must be <kbd class="ph userinput">image</kbd>. |
| EnableSearch | Option to display the search bar. The value must be true or false. |
| SearchPlaceholder | Text that appears in a search bar as a placeholder. |
| SearchType | Defines the query used for search. The value can be <kbd class="ph userinput">starts_with</kbd> or <kbd class="ph userinput">contains</kbd>. If this attribute isn't configured, the instance uses starts_with by default on the display label column. |
[ ]

{#parameter-screen-var-attr__table_gdn_4br_b4b}

## Custom map inputs {#parameter-screen-var-attr__section_txl_qxn_c5b}

|-|-|
| Use custom map inputs to add a link to an indoor map in your mobile app. Users can use these maps to get directions to and reserve resources such as desks, meeting rooms, or lockers. Admins can also configure a parametrized data item with query conditions that enable sorting and filtering of the custom map input. Important: Custom map inputs that support parametrized data items must only use the ScreenId attribute. Don't use any other type of attribute for custom map inputs that support parametrized data items. If you're modifying an existing custom map input that uses the advanced reference qualifier to use a parametrized data item, use the ScreenId attribute only and remove all other attributes. |   |
[ ]

{#parameter-screen-var-attr__table_cust_map_b4b}  
You can use these attributes with custom map inputs.  
Note:  
You can add the custom map input type to your mobile app by using Mobile App Builder, but you must configure the attributes in the platform web UI of your instance.
{#parameter-screen-var-attr__table_w3f_lh4_c5b__entry__2}

| Attribute | Description |
|-|-|
| CustomMapConfigId | The sys_id of the sys_sg_custom_map_config table. |
| CustomMapDefaultProviderId | The sys_id of the provider record in the sys_sg_custom_map_provider table. |
| CustomMapInputs | The sys_id of the floor in the sys_sg_input table. This value must be entered as a JSON array. |
| ScreenId | The sys_id of a parameterized data item used to sort and filter custom map inputs. Important: This attribute can't be used with any other custom map input attribute. If you use the ScreenId attribute with a custom map input, don't use any other attributes with the input. |
| TargetTable | Set to <kbd class="ph userinput">sn_wsd_core_space</kbd>. |
[ ]

{#parameter-screen-var-attr__table_w3f_lh4_c5b}

## Date/time inputs {#parameter-screen-var-attr__section_txk_hww_b4b}

|-|-|
| Use date/time inputs to enable your users to input date and time values. You can configure the input for date and time, or date only. | ![Examples of date and date time configurations.]() |
[ ]

{#parameter-screen-var-attr__table_uxk_hww_b4b}

You can use these attributes with date/time inputs.
{#parameter-screen-var-attr__table_wxk_hww_b4b__entry__2}

| Attribute | Description |
|-|-|
| RenderType | Specify a render type for the date/time input. date-time :   Displays date and time. If no RenderType is defined, this option is the default. date :   Displays only the date. |
| IncludeTimezone | The time zone of the mobile device where the input is being added. The value must be true or false. When set to true, the mobile client sends the Device Time Zone information along with the date and time value to the back-end instance in the following format: YYYY-MM-DDThh:mm:ss.sssTZD Note: The Device Time Zone is different from the User Profile Time Zone that is configured on the platform. If this attribute is not configured, the mobile client doesn't include Device Time Zone information in the date/time input values. This behavior is the default. The date/time input values are in the following format: YYYY-MM-DD hh:mm:ss For information about setting up the IncludeTimezone attribute of date/time inputs for different action types, see [Date/time input setup for different action item types](https://www.servicenow.com/docs/wWPc_9ob8sYpZroMJjPZVw "After you create an input form screen and define its IncludeTimezone attribute for date/time inputs, you must associate the input form screen with an action item. How you set up the date/time inputs depends on the type of action item you use."). For information about action item types, see [Configure an action item](https://www.servicenow.com/docs/Dz0EoyvQQ5zMHMEeAoC_xw "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."). |
| MaxRangeDays | Optional attribute that determines whether future dates can be selected when a date/time input is added. This attribute supports both positive and negative integer values. Setting MaxRangeDays to <kbd class="ph userinput">0</kbd> prevents users from selecting future dates and restricts them to current or past dates. Note: MaxRangeDays can be used together with MinRangeDays, MaxRangeHours, and MinRangeHours. |
| MinRangeDays | Optional attribute that determines whether past dates can be selected when a date/time input is added. This attribute supports both positive and negative integer values. Setting MinRangeDays to <kbd class="ph userinput">0</kbd> prevents users from selecting past dates and restricts them to current or future dates. Note: MinRangeDays can be used together with MaxRangeDays, MaxRangeHours, and MinRangeHours. |
| MaxRangeHours | Optional attribute that determines whether future hours can be selected when a date/time input is added. This attribute supports both positive and negative integer values. Setting MaxRangeHours to <kbd class="ph userinput">0</kbd> prevents users from selecting future date times and restricts them to current or past date times. Note: MaxRangeHours can be used together with MaxRangeDays, MinRangeDays, and MinRangeHours. |
| MinRangeHours | Optional attribute that determines whether past hours can be selected when a date/time input is added. This attribute supports both positive and negative integer values. Setting MinRangeHours to <kbd class="ph userinput">0</kbd> prevents users from selecting past date times and restricts them to current or future date times. Note: MinRangeHours can be used together with MaxRangeDays, MinRangeDays, and MaxRangeHours. |
[ ]

{#parameter-screen-var-attr__table_wxk_hww_b4b}

## Number inputs {#parameter-screen-var-attr__section_ubp_c1r_b4b}

|-|-|
| Use number inputs to enable your users to enter numerical values. Define optional minimum and maximum values to define a number range for your input. You can optionally configure a number input to appear as a percentage. By default, number inputs support decimals. | ![Examples of number inputs configured as a numerical or percentage values.]() |
[ ]

{#parameter-screen-var-attr__table_wln_n4w_b4b}

You can use these attributes with number inputs.
{#parameter-screen-var-attr__table_qmz_d1r_b4b__entry__2}

| Attribute | Description |
|-|-|
| CustomErrorMessage | Sets a custom error message that you can specify. This message displays when the associated UI rule condition is met. |
| Max | Specify a maximum value for the input. |
| Min | Specify a minimum value for the input. |
| RenderType | Specify a render type for the number input. percentage :   Displays a percent symbol(%) after the number in the input. line :   Displays the input as a line field. box :   Displays the input as a box field. integer :   Displays whole integers, such as `3`, `1003`, or `57`. When integer is used, end users can only enter integers and can't enter decimals. |
| SkipValidationWhenHidden | Can be set to either <kbd class="ph userinput">true</kbd> or <kbd class="ph userinput">false</kbd>. It's set to <kbd class="ph userinput">false</kbd> by default, which means that by default the associated UI rule validation is run on the hidden inputs. Only set this to <kbd class="ph userinput">true</kbd> when you want to skip the validation on hidden inputs. |
[ ]

{#parameter-screen-var-attr__table_qmz_d1r_b4b}

## Ranking inputs {#parameter-screen-var-attr__section_xmw_vxw_b4b}

|-|-|
| Use ranking inputs to enable your users to sort the available choices in order of preference or priority. Users tap and drag the available choices. Choices for the ranking input must be manually defined. |   |
[ ]

{#parameter-screen-var-attr__table_ymw_vxw_b4b}

There are no attributes for ranking inputs other than the general attributes listed in this topic.

## Reference inputs {#parameter-screen-var-attr__section_ktz_hbw_b4b}

Use reference inputs for inputs that reference a field on a table. These inputs work like reference fields in the forms on your instance. You can configure your reference input with conditions, reference qualifiers, and a search option to help your users find what
they need quickly.

The optional search option uses "For text" keyword searches and can search for elements within the mobile view.

You can use these attributes with reference inputs.
{#parameter-screen-var-attr__table_pn1_xdt_v4b__entry__2}

| Attribute | Description |
|-|-|
| SourceTable | The source table for your reference qualifier. |
| SourceFieldName | The field name of the referenced field in the source table. |
| TargetTable | The table that you want to target for your reference qualifier. |
[Table 1. Required attributes]

{#parameter-screen-var-attr__table_pn1_xdt_v4b}

The following additional attributes are optional:
{#parameter-screen-var-attr__table_anh_jbw_b4b__entry__2}

| Attribute | Description |
|-|-|
| MultiSelect | Option to enable users to select multiple choices for the input. The value must be true or false. |
| MobileViewId | Mobile view ID (View config) to use for reference list items​. |
| EnableSearch | Option to display the search bar. The value must be true or false. |
| SearchPlaceholder | Text that appears in a search bar as a placeholder. |
| Conditions | Enter an encoded query to apply conditions to your reference list. For details on creating these queries, see Encoded query strings. |
| SearchType | Defines the query used for search. The value can be <kbd class="ph userinput">starts_with</kbd> or <kbd class="ph userinput">contains</kbd>. If this attribute isn't configured, the instance uses starts_with by default on the display label column. |
[Table 2. Extra attributes]

{#parameter-screen-var-attr__table_anh_jbw_b4b}  
This example creates an input form screen input for the Assigned to field on the Incident \[incident\] table. To create this input, you use the three required attributes: TargetTable,
SourceTable, and SourceFieldName.

1. Your users select from a list of users to assign the incident to. So, you set the TargetTable attribute to <kbd class="ph userinput">sys_user</kbd>.
2. Because you're adding the user to an incident record, the SourceTable attribute is set to <kbd class="ph userinput">incident</kbd>.
3. Set the SourceFieldName to <kbd class="ph userinput">assigned_to</kbd> so that the selected user is assigned to the Assigned to field.

{#parameter-screen-var-attr__ol_tdq_b4t_v4b} Figure 5. Reference input for the assigned_to field configured in Mobile App Builder Figure 6. Reference input attributes for the assigned_to field configured in Mobile App Builder

## Signature inputs {#parameter-screen-var-attr__section_hcp_xwc_tvb}

Use signature inputs to capture e-signatures on an input form screen. Signature inputs can be included on input form screen sections or pages.
Figure 7. Signature inputs in an input form screen on a mobile device

You can use the optional IsOverlay attribute with signature inputs. By default, signatures are rendered in the full modal window. When the IsOverlay attribute
Value is set to <kbd class="ph userinput">true</kbd>, signatures are rendered in a half modal window.
{#parameter-screen-var-attr__table_isp_vxc_tvb__entry__2}

| Attribute | Description |
|-|-|
| IsOverlay | Sets whether the signature input is opened in a half modal window. You can set the Value to <kbd class="ph userinput">true</kbd> or <kbd class="ph userinput">false</kbd>. A value of true configures the signature to open in a half modal window. Note: If the 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 isOverlay attribute is ignored, and the signature input is displayed in the full screen. |
[ ]

{#parameter-screen-var-attr__table_isp_vxc_tvb}  
For information about creating an input form screen with signature inputs, see [Configure input form screens with signature inputs](https://www.servicenow.com/docs/9JitccpA4BNMXz~bzyBO8A "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.").  
Note:  
The data source loading mechanism, which uses the DataSouceId and ElementIdentifier attributes is not compatible with signature inputs.

## String inputs {#parameter-screen-var-attr__section_isd_q1r_b4b}

|-|-|
| Use string inputs for text input. You can define a maximum character length for this input. | ![String input example.]() |
[ ]

{#parameter-screen-var-attr__table_jqf_nsw_b4b}

You can use these attributes with string inputs.
{#parameter-screen-var-attr__table_jsd_q1r_b4b__entry__2}

| Attribute | Description |
|-|-|
| Inline | Option to show the input inline, or to open the input in a separate modal. The value must be true or false. |
| MaxLength | Maximum number of characters for the input value. |
| ShowDeleteAll | Option to display a delete button whenever there is text in the input field. This value must be true or false, and is set to false by default. |
| ConfirmDeletion | Option to show the user a confirmation message before text is deleted when using ShowDeleteAll. The value must be true or false, and is set to true by default. |
[ ]

{#parameter-screen-var-attr__table_jsd_q1r_b4b}

## Screen inputs {#parameter-screen-var-attr__section_fp4_lxk_wtb}

Use a screen input to transform a list screen into selectable list input. Users can select multiple list items and perform a write-back operation to the cache.

You can use these attributes with screen inputs.
{#parameter-screen-var-attr__table_fdq_vxk_wtb__entry__2}

| Attribute | Description |
|-|-|
| ScreenId | Configures the list screen that is used for the selectable list input. The value is the sys_id of the list screen. |
| GetDataFromParent | Transforms a list screen from a parent screen into the selectable list input. The filters that are applied to the parent list screen are carried over to the screen input. Enter <kbd class="ph userinput">true</kbd> to enable this attribute. By default, it's turned off on the instance. |
[ ]

{#parameter-screen-var-attr__table_fdq_vxk_wtb}