Skip to content
Tutorials Center
My learning

Topics

Lesson 14 of 39 ยท Forms, Lists and UI Policies

Forms and Form Layout

Configure ServiceNow forms: sections and tabs, Form Layout and Form Design, form views, related lists, formatters, personalization and the form context menu.

A form is how a person sees and edits one record. ServiceNow generates a default form from a table's columns, and administrators shape it with a few focused tools. This lesson covers what a form is made of and how to change it safely.

Anatomy of a form

  • Header: the title bar with the record's display value and buttons (Save, Update, Resolve...). Right-click it for the form context menu.
  • Sections (and tabs): groups of fields. Each section has one or two columns of fields.
  • Fields: each field has a label, an input type from its dictionary entry and states such as mandatory (a red asterisk), read-only or hidden.
  • Related lists: tabs below the form listing records that point to this one.
  • Formatters: special components such as the Activity stream or the Process Flow bar.
  • Form buttons and links: UI actions shown at the top or bottom (covered later).

The form context menu (right-click the header or use the menu icon) has options such as Save, Insert / Insert and Stay, Copy sys_id, Reload form, Configure (Form Layout, Form Design, Dictionary, UI Policies, Business Rules, Client Scripts, Related Lists), and Show XML.

Form Layout

Configure > Form Layout opens a slush bucket: the left list is the fields available on the table, the right list is the fields on the form, in order. Use Add, Remove, Up and Down, and --line-- separators or .begin_split entries for column breaks. Press Save.

Use Form Layout for quick changes and when you need precise control of ordering. It also reveals fields that are not on the form yet.

Form Design

Configure > Form Design gives a drag-and-drop canvas. Drag fields from a palette to a section, create sections and tabs, add annotations (a text note shown in the form), and add related lists and formatters. Use it when you want a visual arrangement or an annotation for users.

Both tools write to the same layout records, so either works. A good habit is to pick one tool per team to avoid confusion.

Form sections and tabs

Sections group related fields ("Caller", "Assignment", "Resolution"). Tabs are sections that appear as tab headers when the form has multiple. Keep the first view short: put only the fields the agent needs to triage on the first section, and park the rest on tabs such as "Notes" or "Resolution Information".

A good form

Short Only what the task needs.
Ordered Top to bottom as people work.
Labelled Clear labels and tooltips.
Safe Mandatory only when needed.
1 / 2

Form views

A view is a named layout of the same table. The default view serves everyone; you can create others such as ess (employee self service) or itil for fulfillers, and a different set of fields appears depending on the view chosen. Views are records in sys_ui_view, and a form layout belongs to a table + view. You switch views with the URL parameter sysparm_view=<name>, from a Views option in the form context menu, or through UI actions and rules that choose the view (for example a View Rule that selects a view by role).

Use views to hide technical fields from non-technical users without writing scripts. Note that hiding a field on a view is not security; a user who can read the table can still read it through lists, REST or reports. Use ACLs for real protection.

Python A form layout and views (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

At the bottom of the form, related lists show other tables' records connected by a reference. Add or remove them with Configure > Related Lists: a slush bucket lists every table that has a reference to this one, plus any Relationship you defined. A related list can show an edit button (to add existing records) and New; the first appears only when the user has the right ACLs.

Order them by importance and remove those you do not use; related lists load data, so many of them slow the form.

Personalizing versus configuring

  • Personalize (gear icon): changes only for you: field order in a list, the form's visible fields in some views. It is stored as a user preference.
  • Configure (context menu): changes for everybody. It is captured in your update set and needs admin rights.

Know which one you are using, especially in the instance's shared development environment.

Python Mandatory-field check on submit (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Good practices

  1. Make changes in a named update set (see Scoped Applications and Update Sets).
  2. Do not delete a field from the table just to hide it from a form; remove it from the layout.
  3. Use annotations sparingly and tooltips (hints) for field help.
  4. Test with impersonation: roles can change what is visible.
  5. Prefer UI policies (next lessons) for conditional visibility, not extra form views.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. Where do you reorder the fields on a form for everyone?

    Form Layout (or Form Design) changes the form for all users.
  2. 2. What is a form view?

    Views let the same table show different fields to different audiences.
  3. 3. Is hiding a field in a view a security control?

    Users with read access can still reach the data through lists, reports or APIs.

Summary

  • Forms have a header, sections, fields, related lists and formatters.
  • Form Layout (precise) and Form Design (visual) edit the same layout.
  • Views give different audiences different layouts; they are not security.
  • Configure changes everyone's form, Personalize changes only yours.

Next: Lists and Encoded Queries