Skip to main content

CnIndexPage

The main list page component. Combines a data table (or card grid), filter bar, pagination, mass actions, CRUD dialogs, and a right-click context menu into a single schema-driven page.

Wraps: NcEmptyContent, NcLoadingIcon (from @nextcloud/vue), CnContextMenu

Try it

Loading CnIndexPage playground…

CnIndexPage showing the full list page with filter bar, data table, and right sidebar

CnIndexPage showing the full list page with filter bar, data table with rows, and right sidebar

Props

PropTypeDefaultDescription
titleString(required)Page title
descriptionString''Optional subtitle
showTitleBooleanfalseShow the page header (icon, title, description) inline above the table. When false (default), the title is shown in the sidebar header instead.
iconString''MDI icon name for the page header. Defaults to schema.icon when a schema is provided.
schemaObject | StringnullOpenRegister schema for auto-generating columns, filters, and form fields. In self-fetch mode a String is the schema slug — the resolved schema object then drives column generation.
objectsArray[]Row data. Omitting this prop while register + schema are set switches the page into self-fetch mode — it drives the list off the object store itself.
filterObjectnullSelf-fetch mode only — a base filter map applied to every fetch as a fixed filter (the user's facet filters can't override it). String values of the form "@route.<name>" or ":<name>" resolve to $route.params[<name>]; other values pass through. Re-resolves when $route.params change. Fed from pages[].config.filter in the manifest path. No effect in consumer-managed mode.
quickFiltersArraynullSelf-fetch mode only — array of \{ label, filter, default?, icon? \} rendered as a tab strip above the table (see CnQuickFilterBar). The active tab's filter is merged into every fetch after filter (the tab wins on a colliding key) and before the user's activeFilters (which still narrow within the active tab). String values follow the same "@route.<name>" resolution as filter. First entry with default:true (else index 0) is active on mount; switching tabs re-fetches at page 1 and emits @quick-filter-change. Fed from pages[].config.quickFilters.
paginationObjectnullPagination state (\{ currentPage, totalPages, totalItems, pageSize \})
loadingBooleanfalseLoading state
selectableBooleantrueEnable row selection checkboxes
selectedIdsArray[]Currently selected IDs
viewModeString'table''table' or 'cards'
sortKeyStringnullCurrent sort column key. null means no column is actively sorted.
sortOrderString'asc''asc', 'desc', or null (no sort)
rowKeyString'id'Unique row identifier field
columnsArray[]Manual column definitions (overrides schema)
excludeColumnsArray[]Schema columns to hide
includeColumnsArraynullSchema columns to show (whitelist)
columnOverridesObject\{\}Per-column overrides
actionsArray[]Custom row action definitions. Each entry accepts the runtime {label, icon, handler, …} shape (function-typed handler fires directly) AND the manifest shape with a string handler resolved through customComponents — see "Action handlers" below.
customComponentsObjectnullCustom-component / handler registry. When set takes precedence over the injected cnCustomComponents from a CnAppRoot ancestor. Used to resolve actions[].handler registry names (manifest-actions-dispatch).
emptyTextString'No items found'Empty state message
rowClassFunctionnullCSS class provider for rows
addLabelString''Add button label
inlineActionCountNumber2Number of inline action buttons before overflow menu
showMassImportBooleantrueShow mass import action
showMassExportBooleantrueShow mass export action
showMassCopyBooleantrueShow mass copy action
showMassDeleteBooleantrueShow mass delete action
massActionNameFieldString'title'Field for display names in mass action dialogs
nameFormatterFunctionnullOptional function (item) => string to format item names in dialogs. Overrides massActionNameField when provided. Passed to all delete and copy dialogs.
exportFormatsArray[]Available export formats
importOptionsArray[]Import dialog options
showFormDialogBooleantrueEnable built-in create/edit form dialog
showRequestFeatureBooleantrueShow the built-in "Request a feature" entry in the CnActionsBar overflow. Opens the CnSuggestFeatureModal with surface: "index:<schema>". Requires a CnAppRoot ancestor (repo inject) to open — warns + no-ops otherwise
useAdvancedFormDialogBooleanfalseUse CnAdvancedFormDialog for create/edit (properties table, JSON tab, optional metadata) instead of CnFormDialog
showViewActionBooleantrueShow the built-in View row action. Emits a dedicated @view event — independent of @row-click. Set to false when the row has no separate "open detail" target.
showEditActionBooleantrueShow edit row action
showCopyActionBooleantrueShow copy row action
showDeleteActionBooleantrueShow delete row action
excludeFieldsArray[]Form fields to hide
includeFieldsArraynullForm fields to show (whitelist)
fieldOverridesObject\{\}Per-field overrides
showAddBooleantrueShow the Add button in the actions bar
addDisabledBooleanfalseDisable the Add button (e.g. when required selections are missing)
refreshDisabledBooleanfalseDisable the refresh button (e.g. when required selections are missing)
showViewToggleBooleantrueShow table/card view toggle
storeObjectnullStore instance for automatic save integration. When provided with objectType, the form dialog saves directly to the store via store.saveObject() instead of only emitting create/edit. The object type must already be registered in the store via registerObjectType().
objectTypeString''Object type slug for store integration (e.g. \${registerId}-\${schemaId}). Required when store is set — a console warning is emitted if missing.
sidebarObjectnullManifest-driven sidebar configuration. When set with enabled: true, CnIndexPage auto-mounts an embedded CnIndexSidebar and forwards its props. Shape: \{ enabled, show?, columnGroups?, facets?, showMetadata?, search? \}. show (default true) is the visibility gate — set false to hide the configured sidebar without removing config. When unset (the default), the legacy slot-based pattern is preserved — consumers wire their own CnIndexSidebar at the App.vue level. See Manifest-driven sidebar below.
searchValueString''Current search term forwarded to the embedded sidebar (only relevant when sidebar.enabled).
visibleColumnsArraynullCurrently visible column keys forwarded to the embedded sidebar (only relevant when sidebar.enabled).
activeFiltersObject\{\}Currently active facet filters \{ fieldName: [values] \} forwarded to the embedded sidebar (only relevant when sidebar.enabled).
registerString''Effective register slug for the page. Forwarded as a prop to the resolved cardComponent so bespoke card UIs can match the schema → register pair. Manifest-driven path: pages[].config.register flows in via CnPageRenderer.
cardComponentString''Optional name of a consumer-provided card component (registered in the customComponents registry on CnAppRoot) to render in place of the default CnObjectCard when the page is in card-grid view mode. Resolution priority: #card scoped slot → cardComponent registry entry → default CnObjectCard. Unknown names log a console.warn once and fall back to the default so a misconfigured manifest never blanks the grid. See Bespoke card-grid below.
customComponentsObjectnullOptional explicit customComponents registry. Overrides the registry injected from CnAppRoot via cnCustomComponents. Mostly used by unit tests; production consumers register components on CnAppRoot instead.

Events

EventPayloadDescription
addAdd button clicked (backward compat)
createformDataForm dialog create confirmed. When store integration is active, payload is the saved object returned by the store.
editformDataForm dialog edit confirmed. When store integration is active, payload is the saved object returned by the store.
deleteidSingle delete confirmed
copy\{ id, newName \}Single copy confirmed
mass-deleteids[]Mass delete confirmed
mass-copy\{ ids, pattern \}Mass copy confirmed
mass-export\{ ids, format \}Mass export confirmed
mass-importimportDataMass import confirmed
refreshRefresh button clicked
row-clickrowRow or card clicked. Conceptually distinct from view — handle row interaction here (selection, expand, drilldown).
viewrowBuilt-in View row action triggered. Conceptually "open the detail view of this row"; bind alongside row-click (with the same handler) when click-to-view is desired.
sort\{ key, order \}Sort changed. Cycles through asc → desc → null (disabled). When cleared, both key and order are null.
page-changedpageNumPagination page changed
page-size-changedsizePage size changed
selectids[]Selection changed
action\{ action, row \}Custom row action triggered
searchtermSearch input changed in the embedded sidebar (only emitted when sidebar.enabled).
columns-changekeys[]Visible columns changed in the embedded sidebar (only emitted when sidebar.enabled).
filter-change\{ key, values \}Facet filter changed in the embedded sidebar (only emitted when sidebar.enabled).
quick-filter-changeindexZero-based active tab index changed (only emitted when quickFilters is set). The fetch is automatically triggered — listen for observability / analytics.

Slots

SlotScopeDescription
#below-headerContent rendered between the page header and the actions bar (e.g. status banners, alerts)
#mass-actions\{ count, selectedIds \}Extra mass action buttons
#action-itemsExtra action bar buttons
#header-actionsExtra header buttons
#delete-dialog\{ item, close \}Replace single-item delete dialog
#copy-dialog\{ item, close \}Replace single-item copy dialog
#form-dialog\{ show, item, schema, close \}Replace create/edit dialog (any variant). Use show as a v-if guard so the dialog unmounts after close; otherwise an always-mounted override re-opens when its internal close animation finishes.
#form-fields\{ fields, formData, errors, updateField \}Form content override (CnFormDialog only; ignored when useAdvancedFormDialog is true)
#field-\{key\}-optionoption object propertiesCustom dropdown option rendering for a select field (forwarded to NcSelect #option)
#field-\{key\}-selected-optionoption object propertiesCustom selected option display for a select field (forwarded to NcSelect #selected-option)
#import-fields\{ file \}Extra import dialog fields
#emptyCustom empty state
#card\{ object, selected \}Custom card template (cards view)
#row-actions\{ row \}Custom row actions
#column-\{key\}\{ row, value \}Custom cell renderer per column

Public Methods

MethodDescription
setFormResult(result)Set form dialog result (\{ success?, error? \})
setSingleDeleteResult(result)Set delete dialog result
setSingleCopyResult(result)Set copy dialog result
setMassDeleteResult(result)Set mass delete result
setMassCopyResult(result)Set mass copy result
setExportResult(result)Set export dialog result
setImportResult(result)Set import dialog result
openFormDialog(item)Programmatically open form (null = create)

Usage

<template>
<CnIndexPage
:title="schema?.title || 'Contacts'"
:schema="schema"
:objects="objects"
:pagination="pagination"
:loading="loading"
@row-click="onRowClick"
@create="onCreate"
@edit="onEdit"
@delete="onDelete"
@refresh="onRefresh"
@page-changed="onPageChanged"
@sort="onSort">
<!-- Custom status column rendering -->
<template #column-status="{ row, value }">
<CnStatusBadge :label="value" :colorMap="statusColors" />
</template>
</CnIndexPage>
</template>

Using the advanced form dialog

Set use-advanced-form-dialog to use CnAdvancedFormDialog for Add/Edit (properties table, JSON tab, optional metadata). The same @create and @edit events and setFormResult() apply.

<CnIndexPage
title="Items"
:schema="schema"
:objects="items"
:pagination="pagination"
:loading="loading"
use-advanced-form-dialog
@create="onCreate"
@edit="onEdit"
@refresh="fetchItems"
/>

Store integration

Set store and objectType to have the form dialog save directly to the store. The object type must be registered in the store (via registerObjectType()) before passing the store here. On save, store.saveObject(objectType, formData) is called; the result phase is shown automatically and @create / @edit are still emitted with the saved object on success.

<CnIndexPage
title="Clients"
:schema="schema"
:objects="clients"
:pagination="pagination"
:loading="loading"
:store="objectStore"
object-type="register-schema"
@refresh="fetchClients"
/>

No @create / @edit handlers or setFormResult() calls are needed when store integration is active. You can still listen to @create / @edit for side effects (e.g. refreshing the list) — the payload will be the object returned by the store.

Custom item names in dialogs

When items don't have a simple name field (like audit trails that only have an ID), use nameFormatter to control how items are displayed in delete and copy dialogs:

<CnIndexPage
title="Audit Trails"
:objects="auditTrails"
:columns="columns"
:pagination="pagination"
:name-formatter="(item) => t('openregister', 'Audit Trail #{id}', { id: item.id })"
@delete="onDelete"
@refresh="onRefresh" />

This formatter is passed through to CnDeleteDialog, CnMassDeleteDialog, CnCopyDialog, and CnMassCopyDialog. It takes precedence over massActionNameField.

Read-only listing

Set :show-add="false" to hide the Add button. Combine with disabled row actions and mass actions for a fully read-only page.

<CnIndexPage
title="Entities"
:objects="entities"
:columns="columns"
:pagination="pagination"
:loading="loading"
:show-add="false"
:selectable="false"
:show-edit-action="false"
:show-copy-action="false"
:show-delete-action="false"
:show-form-dialog="false"
:show-mass-import="false"
:show-mass-export="false"
:show-mass-copy="false"
:show-mass-delete="false"
@row-click="onRowClick"
@refresh="onRefresh"
@page-changed="onPageChanged" />

Hiding built-in actions from a manifest

Manifest type:'index' pages can hide individual built-in actions without writing a wrapper component. The renderer (CnPageRenderer.resolvedProps) flattens config.actionToggles.* into the matching show* / selectable props before mounting CnIndexPage. Explicit config.<key> wins over config.actionToggles.<key> (precedence mirrors the existing config.readOnly shortcut).

{
"id": "Catalogs",
"route": "/catalogi",
"type": "index",
"title": "Catalogs",
"config": {
"register": "opencatalogi",
"schema": "catalog",
"actionToggles": {
"showEditAction": false,
"showCopyAction": false,
"showDeleteAction": false,
"showMassImport": false,
"showMassExport": false,
"showMassCopy": false,
"showMassDelete": false
}
}
}

Known keys (each maps to the matching CnIndexPage prop): showAdd, showFormDialog, showEditAction, showCopyAction, showDeleteAction, showMassImport, showMassExport, showMassCopy, showMassDelete, showViewToggle, selectable. Unknown keys pass validation (forward-compat).

For a fully read-only page, prefer the all-or-nothing shortcut:

"config": { "register": "...", "schema": "...", "readOnly": true }

This expands to nine show*: false defaults; explicit config.showAdd: true still re-enables a specific button.

Self-fetch mode

A manifest type:"index" page dispatches to CnIndexPage via CnPageRenderer, which spreads pages[].config (register, schema, columns, sidebar, actions, filter) plus $route.params — but never an objects prop. So when register and schema are both set and the caller did not pass objects, CnIndexPage self-fetches: it derives objectType = '${register}-${schema}', registers it in the object store, and drives the whole list (collection fetch, _search/_order/_page/_limit, facet filters, schema load, sidebar wiring, the on* handlers) through useListView against the store provided by an ancestor CnAppRoot.

{
"type": "index",
"title": "Decisions",
"config": {
"register": "decidesk",
"schema": "decision",
"sidebar": { "enabled": true }
}
}

In this mode the page's rows, loading, pagination, schema, sort and search term all come from the useListView instance rather than from props; @search / @sort / @page-changed / @filter-change / @refresh route to its handlers (and still $emit for observers).

Form save (create/edit), mass export, and mass import are also self-handled in this mode, because the manifest path has no parent listening for @create / @edit / @mass-export / @mass-import. Confirming the export dialog downloads the register/schema's objects in the chosen format from OpenRegister's /api/objects/{register}/{schema}/export?type= endpoint; confirming the import dialog uploads the file to /api/registers/{register}/import (multipart; the schema slug is added for CSV) and refreshes the list. Both resolve their dialog with no consumer handler required. In consumer-managed mode (objects supplied) @mass-export / @mass-import still just emit for the parent to handle.

Scoping a list to a parent — config.filter

config.filter becomes the filter prop and is applied to every fetch as a fixed filter (a user's facet selection for the same key cannot override it). String values of the form "@route.<name>" or ":<name>" resolve against $route.params; everything else is passed through literally. The filter re-resolves when $route.params change, so a list nested under a parent route (/forms/:id/submissions, /automations/:id/history) is a fully declarative type:"index" page:

{
"type": "index",
"title": "Submissions",
"route": "/forms/:id/submissions",
"config": {
"register": "pipelinq",
"schema": "intakeSubmission",
"filter": { "intakeForm": "@route.id", "archived": false }
}
}

Consumer-managed mode is unchanged

When the objects prop is supplied (every current consumer), nothing changes — no useObjectStore / useListView call, no registerObjectType / fetchCollection, objects and the other props are used as today and filter has no effect. The switch is purely "did the caller pass objects?".

Context Menu

Right-clicking any table row opens a context menu at the cursor position with the same actions as the three-dot row action menu. The context menu renders the mergedActions computed (app-provided actions + built-in Edit/Copy/Delete), so it stays in sync automatically — no app-side changes needed.

Powered by the CnContextMenu component and useContextMenu composable. The composable handles cursor positioning via CSS custom properties; the component renders the NcActions menu.

  • Each action's disabled state (boolean or function) is respected
  • Destructive actions are styled with --color-error
  • The menu closes on action click or outside click, cleaning up the CSS properties and data attribute
  • Works out of the box for all consumer apps (OpenRegister, Doriath, etc.)

Manifest-driven sidebar

Set the sidebar prop to an object to auto-mount an embedded CnIndexSidebar. This keeps the sidebar reachable from manifest.json (pages[].config.sidebar) without consumer apps wiring it manually.

<CnIndexPage
title="Decisions"
:schema="schema"
:objects="decisions"
:sidebar="{
enabled: true,
columnGroups: extraColumnGroups,
facets: facetData,
showMetadata: true,
search: { searchPlaceholder: 'Find decisions...', filtersLabel: 'Refine' },
}"
:search-value="searchTerm"
:visible-columns="visibleColumns"
:active-filters="activeFilters"
@search="onSearch"
@columns-change="onColumnsChange"
@filter-change="onFilterChange" />
sidebar fieldForwarded to CnIndexSidebar asNotes
enabled(existence gate)When false (or missing), the embedded sidebar is NOT mounted — the legacy slot-based pattern still works.
show(visibility gate)Defaults to true. When false, the embedded sidebar is suppressed even if enabled: true. See show vs enabled below.
columnGroupscolumnGroupsExtra column groups beyond schema properties + Metadata.
facetsfacetDataLive facet data \{ fieldName: \{ values: [\{value, count\}] \} \}.
showMetadatashowMetadataDefaults to true.
search(spread via v-bind)Sub-fields like searchPlaceholder, searchTabLabel, searchLabel, filtersLabel map 1:1 onto matching CnIndexSidebar props.

@search, @columns-change, and @filter-change from the embedded sidebar re-emit on CnIndexPage, so consumer event handling stays at the page level.

If you prefer to mount your own CnIndexSidebar (e.g. at the App.vue level for cross-page state), simply leave sidebar unset — the legacy slot-based pattern is unchanged.

show vs enabled

enabled and show answer different questions and are intentionally kept distinct:

  • enabledexistence gate: does this page configure an embedded sidebar at all? When false (or unset), the auto-mount code path is bypassed entirely — no <CnIndexSidebar> is rendered, and the consumer's slot-based pattern stays active.
  • showvisibility gate: should the configured sidebar be rendered right now? Defaults to true. When false, the sidebar config is preserved (so a parent watcher / feature flag can flip back to true later) but the visible surface is suppressed.

Concrete example: a consumer wants the sidebar on wide viewports and hidden on narrow ones. Keep enabled: true, columnGroups: [...] static and toggle show from a layout watcher — the columnGroups / facets / search config is retained across flips.

Action handlers (manifest-actions-dispatch)

actions[] items declared in pages[].config.actions (manifest path) accept a string handler that resolves through the customComponents registry passed to CnAppRoot / CnPageRenderer. The same registry already used to resolve headerComponent / actionsComponent / slot overrides.

Registry-name handler

Manifest declaration:

{
"id": "Queues",
"route": "/queues",
"type": "index",
"title": "Queues",
"config": {
"register": "pipelinq",
"schema": "queue",
"actions": [
{ "id": "process", "label": "Process queue", "handler": "queueProcessHandler" }
]
}
}

Registry entry (e.g. src/customComponents.js):

export function queueProcessHandler({ actionId, item }) {
// open the right modal, dispatch a store action, etc.
store.processQueue(item.id)
}

export default {
// …existing component entries…
queueProcessHandler,
}

When the user clicks "Process queue" on a row, CnIndexPage looks up queueProcessHandler in the registry, sees a function, and calls it with { actionId: "process", item: row }. The page's @action event still fires for any external listeners.

Reserved keywords

Three keywords short-circuit the registry lookup:

  • "navigate" — calls $router.push({ name: action.route, params: { id: row[rowKey] } }). The route field is required when this keyword is set.
  • "emit" — explicit no-op handler that just bubbles @action. Identical to leaving handler unset, but makes intent visible in the manifest.
  • "none" — disables the action click entirely (no handler call, no @action emit).

Example:

{
"actions": [
{ "id": "view", "label": "Open", "handler": "navigate", "route": "QueueDetail" },
{ "id": "z", "label": "Z", "handler": "emit" },
{ "id": "x", "label": "X", "handler": "none" }
]
}

Fallback semantics

  • Missing handler name in the registry → silent fall-through to @action-only (no warning; preserves v1.2 manifests).
  • Non-function entry in the registry (e.g. a Vue component) → console.warn + fall-through to @action-only.
  • Function-typed handler (passed via the runtime prop, NOT through the manifest) keeps working unchanged — used by the built-in view / edit / copy / delete actions.

Bespoke card-grid via cardComponent

The default card-grid view renders CnObjectCard for each row using the page's schema. When that's not enough — e.g. softwarecatalog's Organisaties page needs a profile-style card with a logo, contactpersoon block, and a CTA button — point the manifest at a consumer-provided card component:

// src/customComponents.js
import OrganisatieCard from './components/cards/OrganisatieCard.vue'
export const customComponents = \{ OrganisatieCard \}
<!-- App.vue -->
<CnAppRoot
:manifest="manifest"
app-id="softwarecatalog"
:custom-components="customComponents">
<router-view />
</CnAppRoot>
// src/manifest.json — pages[]
\{
"id": "organisaties",
"route": "/organisaties",
"type": "index",
"title": "Organisaties",
"config": \{
"register": "softwarecatalog",
"schema": "organisation",
"cardComponent": "OrganisatieCard"
\}
\}

The resolved card component receives \{ item, object, schema, register, selected \} props and emits click (forwarded as row-click on the page) and select (forwarded as select on the page). item and object are aliases of each other; pick whichever feels natural.

Resolution priority (highest first):

  1. #card scoped slot — App.vue overrides always win.
  2. cardComponent registry entry — manifest-driven dispatch.
  3. CnObjectCard — the schema-driven library default.

Unknown cardComponent names log console.warn once and fall back to the default so a misconfigured manifest never blanks the grid.

Two-Phase Pattern

CnIndexPage uses the two-phase dialog pattern for all actions:

  1. User triggers action → dialog opens
  2. App handles the event (API call)
  3. App calls setResult() on the component ref
<template>
<CnIndexPage ref="indexPage" @delete="onDelete" />
</template>

<script>
export default {
methods: {
async onDelete(id) {
try {
await this.objectStore.deleteObject('contact', id)
this.$refs.indexPage.setSingleDeleteResult({ success: true })
} catch (error) {
this.$refs.indexPage.setSingleDeleteResult({ error: error.message })
}
},
},
}
</script>

Set documentationUrl (and optionally documentationLabel) to surface a Documentation entry in the CnActionsBar overflow menu, alongside the built-in Request-a-feature item. It opens the link in a new tab. Empty (the default) hides it.

Reference (auto-generated)

The tables below are generated from the SFC source via vue-docgen-cli. They reflect what's actually in CnIndexPage.vue — props, events, and named slots — and update automatically whenever the component changes (see CLAUDE.md "Documenting components").

Props

NameTypeRequiredDefaultDescription
titlestringPage title
descriptionstring''Optional description shown below the title
showTitlebooleanfalseWhether to show the page header (icon, title, description) inline. When false (default), the title is shown in the sidebar header instead.
iconstring''Optional MDI icon name. Defaults to schema.icon when a schema is provided.
schemaobject&#124;stringnullSchema. Either a resolved schema object (consumer-managed path) OR a schema-slug string — when a string is given together with register and no objects prop, the page enters self-fetch mode: it drives the list via useListView('\${register}-\${schema}', …) and the column generation uses the schema object that composable loads. Backwards- compatible: [Object, String] still accepts an object.
filterobjectnullBase filter for the self-fetch path. String values of the form "@route.&lt;name&gt;" / ":&lt;name&gt;" are interpolated from $route.params.
quickFiltersarraynullSelf-fetch mode only — an array of clickable filter tabs rendered as a strip above the table. Each entry is {label, filter, default?, icon?}; clicking a tab merges its filter into the fetch — spread AFTER filter (so the active tab wins) and BEFORE the user's activeFilters (so user facets still narrow within the active tab). String values in a tab's filter resolve @route.&lt;name&gt; / :&lt;name&gt; from $route.params just like the filter prop. The first tab with default:true (else index 0) is active on mount; changing tabs re-fetches at page 1. Omit (or null) → no tab strip, behaviour unchanged.
columnsarray[]Manual column definitions (used instead of schema when provided)
objectsarray[]Object/row data array
paginationobjectnullPagination state: { page, pages, total, limit }
loadingbooleanfalseWhether data is loading
selectablebooleantrueWhether rows/cards can be selected
selectedIdsarray[]Currently selected IDs
viewModestring'table'View mode: 'table' or 'cards'
sortKeystringnullCurrent sort key
sortOrderstring'asc'Current sort order
rowKeystring'id'Unique row identifier property
excludeColumnsarray[]Columns to exclude in schema mode
includeColumnsarraynullColumns to include in schema mode (whitelist)
columnOverridesobject\{\}Per-column overrides in schema mode
actionsarray[]Row action definitions (app-provided, merged with built-in actions)
emptyTextstring'No items found'Text shown when no items found
rowClassfuncnullFunction returning CSS class(es) for a row
addLabelstring''Override label for the Add button. Defaults to "Add {schema.title}"
inlineActionCountnumber0How many action buttons to show inline (rest go in overflow dropdown)
showMassImportbooleantrueWhether to show the built-in mass Import action
showMassExportbooleantrueWhether to show the built-in mass Export action
showMassCopybooleantrueWhether to show the built-in mass Copy button
showMassDeletebooleantrueWhether to show the built-in mass Delete button
massActionNameFieldstring'title'Property name used to display item names in dialogs
nameFormatterfuncnullOptional function to format item names in dialogs. Receives the item, returns a string. Overrides massActionNameField when provided.
exportFormatsarray[ \{ id: 'excel', label: 'Excel (.xlsx)' \}, \{ id: 'csv', label: 'CSV (.csv)' \}, ]Available export formats for the export dialog
importOptionsarray[]Import option definitions for the import dialog
showFormDialogbooleantrueWhether to show the built-in form dialog for Add/Edit
useAdvancedFormDialogbooleanfalseUse CnAdvancedFormDialog (properties table, JSON tab, optional metadata) instead of CnFormDialog for Add/Edit
showViewActionbooleantrueWhether to add a View action to row actions. The action emits a dedicated view event — independent of row-click. Bind @view to handle "open detail" and @row-click to handle row click (selection, expand, etc.); they may share a handler when the app wants click-to-view, but they are conceptually distinct.
showEditActionbooleantrueWhether to add an Edit action to row actions
showCopyActionbooleantrueWhether to add a Copy action to row actions
showDeleteActionbooleantrueWhether to add a Delete action to row actions
excludeFieldsarray[]Field keys to exclude from the form dialog
includeFieldsarraynullField keys to include in the form dialog (whitelist mode)
fieldOverridesobject\{\}Per-field overrides passed to CnFormDialog
showViewTogglebooleantrueWhether to show the Cards/Table view toggle in the actions bar
refreshingbooleanfalseWhether the refresh action is currently in progress
refreshDisabledbooleanfalseWhether the refresh action is disabled (e.g. when required selections are missing)
addDisabledbooleanfalseWhether the Add button is disabled (e.g. when required selections are missing)
showAddbooleantrueWhether to show the Add button in the actions bar
storeobjectnullStore instance for automatic save integration. When provided alongside objectType, the form dialog saves directly to the store instead of emitting create/edit events. The object type must already be registered in the store via registerObjectType() before passing the store here.
objectTypestring''Object type slug for store integration (e.g. \${registerId}-\${schemaId}). Required when store is set — a console warning is emitted if missing.
sidebar{ enabled: boolean, show?: boolean, columnGroups?: Array, facets?: object, showMetadata?: boolean, search?: object }&#124;nullnullManifest-driven sidebar configuration. When set with enabled: true, CnIndexPage auto-mounts an embedded CnIndexSidebar wired to the page's schema, search, columns, and facet props. When unset or enabled: false, the legacy slot-based interface is preserved — consumers mount their own CnIndexSidebar at the App.vue level. Shape: - enabled (boolean) — existence gate. Whether the page configures an embedded sidebar at all. When false or unset, the auto-mount path is bypassed (no &lt;CnIndexSidebar&gt; rendered) and the consumer's slot pattern stays active. - show (boolean, default true) — visibility gate. Even when enabled: true, show: false SUPPRESSES rendering for this page so manifest authors can hide the sidebar declaratively without removing the config. Distinct from enabled so config can be retained (e.g. for a watcher / responsive layout) while the visible surface is hidden. - columnGroups (array) — extra column groups beyond schema + Metadata. - facets (object) — live facet data { fieldName: { values: [...] } }. - showMetadata (boolean) — include the built-in Metadata column group (defaults true). - search (object) — search-related label overrides forwarded to CnIndexSidebar.
searchValuestring''Current search term (forwarded to the embedded sidebar when sidebar.enabled).
visibleColumnsarraynullCurrently visible column keys (forwarded to the embedded sidebar).
activeFiltersobject\{\}Currently active facet filters: { fieldName: [values] } (forwarded to the embedded sidebar).
registerstring''Effective register slug for the page. Forwarded as a prop to the resolved card component (when cardComponent is set) so bespoke card UIs can match the schema → register pair. Manifest-driven path: pages[].config.register flows in via CnPageRenderer's v-bind="resolvedProps" spread.
cardComponentstring''Optional name of a consumer-provided card component (registered in the customComponents registry on CnAppRoot) to render in place of the default CnObjectCard when the page is in card-grid view mode. Resolution priority (highest first): 1. The parent's #card scoped slot (always wins). 2. The component resolved from cardComponent against the effective customComponents registry. 3. The library default (CnObjectCard). Unknown names log console.warn once and fall back to the default so a misconfigured manifest never blanks the grid.
customComponentsunionnullOptional explicit customComponents registry. When set, this overrides the registry injected from CnAppRoot via cnCustomComponents. Provided primarily so unit tests can pass a registry without mounting CnAppRoot. Used by: - cardComponent resolution (REQ-MCI from manifest-card-index) - actions[].handler registry name resolution (REQ-MAD-3 from manifest-actions-dispatch — handler funcs called on row-action click)

Events

NamePayloadDescription
page-size-changed
search
quick-filter-change
sort
page-changed
filter-change
columns-change
refresh
action
row-click
view
add
view-mode-change
select
mass-delete
mass-copy
mass-export
mass-import
delete
copy

Slots

NameBindingsDescription
headertitle, description, icon, show-title
below-header
mass-actionscount, selected-ids
action-items
actions
import-fieldsfile
delete-dialogitem, close
copy-dialogitem, close
form-dialogshow, item, schema, close
form-fields
empty
'column-' + colname, row, value
row-actionsrow
cardobject, selected

Methods

NameDescription
setMassDeleteResult
setMassCopyResult
setExportResult
setImportResult
setDeleteResult
setCopyResult
setSingleDeleteResult
setSingleCopyResult
setFormResult
openFormDialogProgrammatically open the form dialog.
openDeleteDialogProgrammatically open the single-item delete dialog.