Primary interfaces
Summarize
Summary of Primary Interfaces
The primary interfaces for users to interact with data models in ServiceNow are through forms, lists, and mobile applications. These interfaces enable efficient data access and management, enhancing user experience and productivity.
Show less
Key Features
- Forms and Lists: Forms display individual records while lists show multiple records. Configuring these elements effectively is crucial for user engagement.
- Form Configuration:
- Minimize fields to reduce loading times.
- Use form views for different field sets based on context.
- Group fields logically in sections to minimize scrolling.
- Maintain a logical field order (e.g., start date before end date).
- Limit default list columns to seven; users can personalize further.
- Avoid placing reference fields first in list views to prevent navigation issues.
- Mobile Applications: For mobile interactions, utilize the ServiceNow Agent app and Studio to create mobile applications with focused applets, including main screens and detail views.
Key Outcomes
Implementing these best practices leads to improved user experience through faster loading times, intuitive navigation, and organized data presentation. Properly designed forms and mobile applications enhance accessibility and usability, ensuring users can efficiently perform their tasks on both desktop and mobile platforms.
The primary way for users to interact with a data model is through forms and lists or through mobile.
Forms and lists
The standard method of accessing data in ServiceNow is through the default forms and lists. A form displays information from one record in a data table and a list displays a set of records from a table. When configuring forms and lists:
- Keep the number of fields on a form to a minimum. The more fields on a form, the longer the form takes to load resulting in a poor user experience. Use form views to create different sets of fields for different situations.
- Use form sections to logically group fields together and to keep users from scrolling. The top section of the form should contain the fields that are always needed or used, while the other form sections contain less frequently utilized fields.
- Make sure fields appear in the right order. For example, the start date field should always come right before an end date field.
- Use seven or fewer columns in a default list. Users can add more by personalizing their lists.
- Avoid using a reference field as the first item in the list view, because it is shown as hyperlinked text. Clicking on the reference field will redirect the user to the referenced record instead of the list record, resulting in a poor user experience.
This example shows a poorly designed form.
- The form has no sections. Users need to scroll through the entire form to see all the fields.
- Similar fields are not grouped together. For example, Assignment group and Assigned to are on different sides of the form.
This example shows a well-designed form.
- Fields are grouped together logically.
- The form has been broken into sections for easier viewing and data entry.
Mobile
If users will interact with the application on their mobile devices and will need native iOS or Android functionality, such as geolocation or offline access to application data, use the ServiceNow Agent app. Use Studio to create a mobile application for the application.
Self-paced training: Mobile Applications
Other resources: Mobile Resources