Form and List Layout

ui-actions-policies covers behaviour on a form — what happens when a field changes. This covers the shape of it: which fields are on the form, in what order, in which sections, and what the list shows. Nothing covered lists at all before this guide.

Views come first

Almost every table in this guide has a view field, and it is the thing to decide before anything else.

A view is a named layout for one table. The empty string "" is the default view — the one everyone gets. "mobile", "ess" and any custom name are separate layouts on the same table, and editing one changes nothing about the others.

await snow_add_list_column({ table: "incident", element: "u_root_cause" })   // default view: everyone
await snow_create_list_layout({ table: "incident", view: "mobile", columns: [...] })  // mobile only