Lists

The list view is the table that displays many records at once, with filtering, sorting, paging, and bulk operations.

Open it from PF Manage → Entities → [your entity] → Records tab.

Anatomy

Top to bottom:

• Toolbar — saved-view dropdown, filter input (EQL), columns button, layout switcher (table / cards / kanban), bulk actions button, New record button.
• Filter bar — when expanded, shows the active EQL filter as chip-style tokens you can click to edit.
• Header row — column titles. Click to sort, drag to reorder.
• Body — the rows, paginated.
• Footer — pagination + row count.

Layouts

Three layouts, switchable per saved view:

1. Table (default): rows × columns, standard tabular layout. Best for many fields.
2. Cards: each record as a card with selected fields, in a responsive grid. Best for image-heavy entities.
3. Kanban: each record as a card in a column. The column is determined by a Single-choice field (typically status). Drag-and-drop cards between columns to update the field. Best for workflow-style entities (tickets, deals, tasks).

Inline cell edit

Double-click any cell (in Table layout) to edit it in place without opening the full form. Saves on blur (or Esc to cancel).

Cells respect the same validation as the form. If validation fails, the cell stays in edit mode with an inline error.

Bulk operations

Select multiple rows via checkboxes → Bulk actions dropdown:

• Delete selected (with confirmation).
• Update field — set a chosen field to a chosen value across all selected.
• Export selected as CSV / JSON.
• Trigger workflow — pick a workflow that takes a single record as input; the engine runs it once per selected record (in a Batch window node so the queue doesn't drown).

Capability pfm_bulk_operations required. Mapped to manage_options by default.

Saved views

Bundle (filter, columns, sort, layout, grouping) and save with a name. Saved views appear in the toolbar dropdown and as bookmarks users can share by URL. Personal saved views are private; team saved views (capability pfm_share_views) are visible to all users.

CSV import / export

The toolbar ⋯ menu → Import CSV opens a wizard:

1. Upload the CSV.
2. Map CSV columns to entity fields (auto-detect by exact match; you confirm or override).
3. Pick conflict policy: skip duplicates (matched by a chosen field) / update existing / create as new regardless.
4. Dry run shows how many rows would be created / updated / skipped / errored. Click Apply to commit.

Export the current view (with its filter applied) via Bulk actions → Export selected as CSV.