UI: Saved Views

Saved views are part of the UI index experience. They store reusable resource index state for operators.

Storage

The UI package loads UI migrations. Current upgrade notes list seviaflow_saved_views as the saved-view table for new SeviaFlow installs.

Runtime Services

The UI source includes SeviaFlow\Ui\SavedViews\SavedViewRepository and index saved-view services. Resource index tests cover saved-view state management.

Scope

Saved views are UI state. They do not replace Resource table definitions, Core filters or API query parameters.

State contract

Current saved-view state version 2 includes search, validated filters, sortable state, page size, visible column order and trash scope. Views are private to the authenticated user and resource slug. Applying a view revalidates filters, columns, sorting and trash support against the current resource, so stale or tampered state cannot widen record access. The UI marks the selected view as modified when the current list differs from its saved state.