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


---

# List screen

# List screen {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 List Screen

The list screen allows users to display records in a card format, providing a preview of select information.
It is designed for mobile apps, enabling users to easily navigate and interact with records.
Configuration options are available through the Mobile Card Builder (MCB) and Mobile App Builder (MAB).
Show full answer Show less  

## Key Features

* **Record Screen Configuration:** Automatically displays a detailed view of a record when tapped.
* **Mobile List Filters:** Enhances search capabilities for users to find specific records.
* **Dynamic Screen Name:** Configures the header to inherit names from previous selections or fields.
* **Parameterized List Screens:** Passes values into the list screens based on user selections.
* **Functions:** Allows users to perform actions directly on records via swipe, footer, or top menu functions.
* **Default Filters:** Automatically created filters based on selected fields, with options for custom filters.

## Key Outcomes

By utilizing the list screen effectively, ServiceNow customers can enhance user experiences through intuitive navigation, quick access to detailed records, and the ability to perform actions seamlessly. The configuration options provided allow for tailored functionalities that meet specific business needs, improving overall efficiency and satisfaction in mobile applications.  
Use a list to display a list of records. Records in lists display in a card format,
showing a limited selection of the information in the record.

|-|-|
| Use a list screen to see records in a list view. Within a list screen, each record has a card. This card is a visualization which contains a selected few fields that display as a preview for each record. You can configure the card in Mobile Card Builder (MCB). MCB can be accessed from Mobile App Builder (MAB) when creating a list screen. Use the optional features available with list screens to improve your user's experience. Record screen :   Configure your list screen to include a record screen. This configuration automatically displays a detailed view of a record when your users tap it in the list screen. Learn more about record screens in [Record screen](https://servicenow-prod.fluidtopics.net/xGWWpt3H0iUEYOOmpq3WkQ "Record screens display content for a specific single record."). List filters :   Mobile list filters enable your users to find what they need in the records on your instance. For more detail on filters, see [Mobile list screen filters](https://servicenow-prod.fluidtopics.net/~LkRqJSw6j8yaNjq88L8Ww "Use mobile filters in list screens to enable your users to find what they need in your instance's records."). Dynamic screen name :   Configure your list screen to inherit the name of a previous screen selection or form field and display it as the header on a subsequent screen. For more information, see [Configure a dynamic screen name for a list screen](https://servicenow-prod.fluidtopics.net/qWYqoScq7zoQdr6Uz5H8QA "Configure a screen to dynamically inherit a name from a parametrized list screen. This setup enables users to view a passed parameter as the screen name instead of the screen record name."). Functions :   Functions determine which actions users can perform in your mobile apps. For more detail on functions, see [Mobile functions](https://servicenow-prod.fluidtopics.net/hxfkLR_viSp6YqBKbnmguw "Configure functions in Mobile App Builder to determine which actions users can perform in the mobile app."). |   |
[ ]

{#list-screen__table_w4s_g2w_dlb}

## Configure lists with forms {#list-screen__section_b4n_bv3_nlb}

|-|-|
| Configure your list with a record screen so your users can tap list items to view details of the records on your list. For details on list configuration, see [List screen configuration](https://servicenow-prod.fluidtopics.net/gISd3nnYKhWRLpG~7Z9KXg "Configure a list screen so that your users can see a list of records from their mobile app. To access a record from the list, a user can tap the record name."). |   |
[ ]

{#list-screen__table_y4t_zv3_nlb}

## Parametrized list screens {#list-screen__section_blb_gw3_nlb}

|-|-|
| Use parameters to pass information into your list screens. For example, when a user taps on a group in a group list screen, a list containing records in the group is displayed. The list of records in the group is a parametrized list, which accepts the value of the group your user selected as a parameter. To learn about parametrized list configuration, see [Parametrized list screens](https://servicenow-prod.fluidtopics.net/9dMv0LYV3hafsP5ds9nIOw "Learn how to use parameters to pass information into a list screen."). |   |
[ ]

{#list-screen__table_plp_sw3_nlb}

## List screen functions {#list-screen__section_hxw_t1q_slb}

Add functions to your list screens to give your users the ability to take actions directly on
a record screen. List screens support swipe, footer, and top menu functions. For more
information on functions, see [Mobile functions](https://servicenow-prod.fluidtopics.net/hxfkLR_viSp6YqBKbnmguw "Configure functions in Mobile App Builder to determine which actions users can perform in the mobile app.").  

|-|-|
| Swipe functions Use swipe functions to act on a specific record on the list. You can configure one or more actions to appear when a user swipes on a record. You can also configure a different set of actions depending on whether a user swipes to the left or to the right. |   |
| Top menu functions Use top menu actions for less frequently used actions, or actions that apply to the list rather than individual records, such an Approve all action. |   |
| Footer functions Footer functions enable your end users to take an action on a menu item located in a screen's footer region. |   |
[ ]

{#list-screen__table_o45_nbq_slb}

## List screen filters {#list-screen__section_ng2_5ks_dwb}

By default, the instance automaticaaly creates filter and sorting functionality. This filter
is based on the fields selected in your list pattern. No further configuration is needed. Users
can filter and sort the list based on any of these fields.

If the default filters do not fit your requirements, you can create a custom filter. You can
manually select the fields that are available to the list filter and enable keyword filtering.
For more information about list screen filters, see [Mobile list screen filters](https://servicenow-prod.fluidtopics.net/~LkRqJSw6j8yaNjq88L8Ww "Use mobile filters in list screens to enable your users to find what they need in your instance's records.").

## Dynamic screen name {#list-screen__section_hzj_l3w_dlb}

Use dynamic screen name functionality to let users to easily identify the screen or field
which they are currently viewing. You can configure a screen to inherit a name from a previous
screen selection. These dynamic names can be used with grouped lists, where the selected group
name becomes the header on a subsequent screen. Alternatively, a field in a form can be used as
a header in a different screen. For more information, see [Configure a dynamic screen name for a list screen](https://servicenow-prod.fluidtopics.net/qWYqoScq7zoQdr6Uz5H8QA "Configure a screen to dynamically inherit a name from a parametrized list screen. This setup enables users to view a passed parameter as the screen name instead of the screen record name.").  

|-|-|
| Display name from a redirection parameter Use a dynamic screen name to inherit a name from a previous screen selection. In the example, the screen name comes from a list which is grouped by category from a launcher screen. |   |
| Display information from field previous record Use dynamic record screen names to display information from a specific record in a table. The record screen name can come from any field in a database record. In the example, the screen name comes from the incident field. |   |
[ ]

{#list-screen__table_rjt_nmr_ylb}

