{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":34757,"path":"mobile/configure-param-form-applet.md","title":"Configure a parameterized record screen","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure a parameterized record screen\n\nConfigure a record screen to query a user for a parameter. The screen then uses this parameter to determine the record that appears on the screen.\n\n## Before you begin\n\nRole required: admin\n\n## Procedure\n\n1. Navigate to **All** > **System Mobile** > **Mobile App Builder**.\n\n The Mobile App Builder\n\n2. Search for the application scope you are working in and then select the name of the application scope.\n\n The Mobile App Builder\n\n3. Select the **Screens** category, and then select **New**.\n\n4. Select the **Record** option in the Create a screen page, and then select **Continue**.\n\n5. Complete the following fields as needed.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nName\n\n\n\nThe name of your screen. This name appears as a tile in the mobile application.\n\n
\n\nDescription\n\n\n\nAdditional information about your screen.\n\n
\n\nFetch type\n\n\n\nSettings that determine when data is loaded in your screen. Select from the following fetch types:\n\n - **Prefetch:** This option pre-loads record screen data when an end user accesses a list, calendar, or record screen.\n- **On-demand:** The app sends a network request to load the app only when end users navigate to it.\n- **Background**: The app makes a background network request to load embedded screens or record screen segments.\n- **Dynamic prefetch:** Screens for the first 10 rows load as described for the Prefetch fetch type. After the 10 first rows load, additional rows of screens load with the On-demand fetch type.\n\n\n
\n\nDynamic prefetch count\n\n\n\nYou can change the number of rows loaded with prefetch by changing the value of the Dynamic prefetch count field.\n\n
\n\nHide screen name\n\n\n\nOption to hide the record's screen name.\n\n
\n\nView using \\(Legacy Card/Card\\)\n\n\n\nA Card used for the header section of the record screen. Use the Mobile Card Builder to change the appearance of your mobile card or the fields displayed on the card. For more detail on using the Mobile Card Builder, see [Customize a screen using Mobile Card Builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/mcb-customize-item-view.md).\n\n The best practice is using **Card**.\n\n
\n\nCard\n\n\n\nThis is an element that visually displays information from different records. You can style this information by setting specific conditions for each information type.\n\n
\n\nIcon\n\n\n\nIcon that appears in the header of the launcher screen.\n\n
\n\nAlert\n\n\n\nThis is a mobile alert overlay for a record screen. Use it to inform users of an important message and to redirect them to a specific screen. Only one mobile alert is available per instance.\n\n
\n\nData item\n\n\n\nThis defines what table you want data from and what conditions must be met for the data to be displayed.\n\n
\n\nRecord screen segments\n\n\n\nThis is a UI element for switching between different lists on a single record screen. Use it to divide content into different areas on the screen.\n\n
\n\nDynamic segments height\n\n\n\nSets the height for dynamically sized segments.\n\n
\n\nDynamic segments minimum width\n\n\n\nSets the minimum width for dynamically sized segments.\n\n
\n\nTop menu function instances\n\n\n\nFunctions placed in the top menu of the record screen.\n\n
\n\nUI parameters\n\n\n\nThis is a variable that affects how a field or UI element behaves. Use it to determine how a value can be entered or if it will be autopopulated for a UI element based on what the user has done.\n\n
\n\nDynamic screen title\n\n\n\nThis is how you can create an element and map it to a UI parameter. Use it to pass a value from one screen to another and include it in the title of the destination screen.\n\n
\n\nRole access\n\n\n\nOption to limit user access to the screen by role.\n\n
6. On the Record screen form, select an existing data item or create a new one.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nName\n\n\n\nName of the data item.\n\n
\n\nDescription\n\n\n\nAdditional information about your data item.\n\n
\n\nTable\n\n\n\nTable where the data item gets its data from.\n\n
\n\nGroup by\n\n\n\nDetermine what values the table will be grouped by.\n\n
\n\nCondition Type\n\n\n\nWhether the conditions for the data item are declarative, scripted, or use an encoded query. Leave this field at its default setting.\n\n
\n\nOffline condition\n\n\n\nConditions to apply when the user sets the app to offline mode.\n\n
\n\nParameters\n\n\n\nData Parameter used for filtering the data item. Use parameters to accept values passed from screens or other sources.\n\n
7. In the Data item screen, create a new data parameter by selecting the **New** button in the Parameters field.\n\n8. In the New Data Parameter screen, enter a name for your parameter in the **Name** field, and select the parameter **Type**.\n\n The available types are Integer, String, Decimal, Boolean, Datetime, or Date. For more detail on available options when creating parametrized data items, see [Configure a parametrized data item](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/mobile/sg-config-parametrized-data-item.md).\n\n9. Use the left panel hierarchy tree to return to the data item you just created a data parameter for.\n\n In the **Condition** field, create a query that uses your parameter to filter your records.\n\n10. Use the left panel hierarchy tree to return to the Record Screen and select **New** in the **UI Parameters field** to create a new parameter.\n\n11. In the **Properties** section, enter a name for the UI parameter.\n\n12. In the **Setting** section, fill in the following fields.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nInput type\n\n\n\nHow your users enter a value for this parameter. Select from the following options:\n\n - Text\n- Choice List\n- Search List\n- QR/Barcode\n\n\n
\n\nTable name\n\n\n\nTable used for the choice list where users select a parameter value.**Note:** This field is visible only when **Input type** is set to **Choice list** or **Search list**.\n\n
\n\nField name\n\n\n\nThe field used for the choice list where users select a parameter value.**Note:** This field is visible only when **Input type** is set to **Choice list** or **Search list**.\n\n
\n\nDefault value\n\n\n\nDefault value for your parameter.**Note:** This field is only visible when **Default value type** is set to **Manual**.\n\n
\n\nInput style\n\n\n\nInput style for your parameter. Select from **Inline** or **Popup**.\n\n
\n\nDefault value type\n\n\n\nWhether the parameter has a default value. Select **None** to have no default value, or **Manual** to enter a manual value in the **Default value** field.\n\n
\n\nMandatory\n\n\n\nDetermines whether user input for the parameter is mandatory.\n\n
\n\nPlaceholder text\n\n\n\nText that appears in the parameter entry field before the users enters a value.\n\n
\n\nMulti-select\n\n\n\nWhether the user can select multiple values from the choice list.**Note:** This field is visible only when **Input type** is set to **Choice list**.\n\n
\n\nSearch type\n\n\n\nThe type of search used when finding a parameter value.**Note:** This field is visible only when **Input type** is set to **Search list**.\n\n
\n\nCarried\n\n\n\nWhether this parameter a carried parameter. Use carried parameters to move information between different screens and actions.\n\n
13. In the **Data Parameter Mapping** section, select the **Choose** button to create a new parameter mapping.\n\n14. Select the data parameter you created for the data item.\n\n15. Select **Apply**.\n\n16. Select **Save**.\n\n\n## Result\n\nThe UI parameter in your form is associated with the data parameter in your data item. When a user accesses this form, the screen prompts the user for a value for the parameter. The data item uses that value to filter the record displayed in the form.\n\n"}}