# List View

List View embeds **live ServiceNow data** directly into your board as a tabular view. Instead of drawing a shape per record, you drop a table into a List View container and every matching record appears as a row — automatically refreshed when the underlying ServiceNow data changes.

Use List View when:

* You want to show a **dataset alongside a diagram** (e.g. a capability map on the left, a list of supporting applications on the right).
* The records are too many for a useful node-and-link view.
* Stakeholders need to see **specific field values** like steward, user base, lifecycle status in a scannable grid.
* The data will change frequently and you want the visualization to track ServiceNow without manual updates.

## Adding a List View

1. Open the left sidebar and click **Visualizations**.
2. Drag the **List View** tile onto the canvas (or click-then-click to place).
3. An empty List View container appears with the prompt *"Open the Data Hub and place your items here…"*

<figure><img src="/files/R68jMAVmv37nqyzPj2Gn" alt=""><figcaption></figcaption></figure>

## Populating the List View

1. Click the **Data Hub** icon in the control bar to open the Data Hub.
2. Select the **table** you want to list (e.g. Business Application).
3. Drag either:
   * The **table name** — shows every record of that type (subject to filters)
   * A **specific record** — narrows the list to that single item's details
4. Drop onto the List View container.

The list populates with rows from ServiceNow.

## What Appears in the List

Each row shows the ServiceNow record's field values, laid out in columns. The columns default to the fields configured for the shape (see [Shape Fields](/models/admin/shape-fields.md) on the admin side). Sample columns for a Business Application table might include:

* Data Currentness
* Steward
* User base
* Internal Lifecycle
* Data Completeness
* Name
* Description

## Pagination

Large result sets are paginated inside the List View container:

* **Rows per page** — adjustable at the bottom of the list
* **Page navigation** — `<` and `>` arrows with a "1–10 of 80"-style range indicator
* Users inside the board (edit or presentation mode) can flip pages without leaving the board.

## Live Updates

Data in the List View reflects the current state of the ServiceNow records at load time and refreshes when the board is reopened or a record-watcher update fires. Edits to records in ServiceNow appear automatically — no manual diagram refresh.

This makes List View a useful companion to dashboards that need to stay accurate even when the diagram author isn't actively editing.

## List View vs. Other Visualizations

| Situation                                            | Use                                                                             |
| ---------------------------------------------------- | ------------------------------------------------------------------------------- |
| Record-level detail, many rows, changes over time    | **List View**                                                                   |
| Parent/child hierarchy                               | [Hierarchy Map](/models/work-in-the-app/editor/visualizations/hierarchy-map.md) |
| Central element with multiple levels of related data | [Context Map](/models/work-in-the-app/editor/visualizations/context-map.md)     |
| Task-flow with status lanes                          | [Kanban Board](/models/work-in-the-app/editor/visualizations/kanban-board.md)   |

List View is intentionally minimal. If you need to highlight anomalies, pair it with [Realtime Indicators](/models/work-in-the-app/editor/realtime-indicators.md) on the individual records, or embed it alongside a relationship-based visualization.

## Tips

* **Use filters to scope the list.** Apply a Data Hub filter before dropping the table to limit what shows up.
* **Combine with a hierarchy or context map** — one side shows structure, the other shows the data detail.
* **Keep the List View reasonably sized.** Very large lists slow board loads; use filters or use pagination deliberately.
* **Check which fields are configured.** If the columns aren't what you expected, the fields shown come from the [Shape Fields](/models/admin/shape-fields.md) configured for the underlying shape — an admin can expose more.

## Limits & Gotchas

* **List View doesn't support drawing relationships from/to rows.** Each row is a live data record, not a draggable shape.
* **Sorting and column customization are limited** in v26 — the list shows the fields configured in Shape Fields, in that order.
* **Locked List Views can't be edited** — lock state hides edit controls; remove the lock to re-target the view.
* **List View respects user ACLs.** Users only see rows they're permitted to read in ServiceNow — if a user's list looks sparse, check their role access to the underlying records.
* **The list is read-only on the board.** Editing a record's fields is done through the [Data Panel](/models/work-in-the-app/editor/data-inspector.md) on a separate shape, or through the ServiceNow form.

## Related

* [Visualizations Overview](/models/work-in-the-app/editor/visualizations.md)
* [Data Hub](/models/work-in-the-app/editor/data-hub.md) — the source of the records displayed
* [Shape Fields](/models/admin/shape-fields.md) — controls which columns appear
* [Hierarchy Map](/models/work-in-the-app/editor/visualizations/hierarchy-map.md)
* [Context Map](/models/work-in-the-app/editor/visualizations/context-map.md)
* [Realtime Indicators](/models/work-in-the-app/editor/realtime-indicators.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ins-pi.com/models/work-in-the-app/editor/visualizations/list-view.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
