BusinessPad

Selected UX case · Модальность

Saved List Views

Turning a set of filters, groupings and columns into a named view that can be reopened in one click, kept personal or shared.

Saved view «Просроченные и запланированные» applied: success message, view chip with a remove button, and the status filter set to «Запланирован»

01 Context

The same list, seen many ways.

Registries in BusinessPad can hold thousands of records. The contractor payments registry in these screens has 1680.

People rarely look at all of them. A finance manager may only want overdue and scheduled payments, grouped by status. Setting that up again every time is repetitive.

Registry «Платежи подрядчикам» with 1680 payments, statuses, stages, dates and amounts
A registry before any view is saved.

02 Problem

Filters are easy to set, hard to keep.

Filters, grouping and columns are configured separately and lost when the user leaves. There was no way to name a combination, come back to it, or give it to colleagues.

03 Design approach

Save what is already on screen.

A modality is a saved configuration of the current list. The user sets up the list as usual, then saves it from the More menu with a name and a description.

Saved views live in a side panel next to the list, split into personal, shared and recommended.

More menu on the registry with settings, edit view, group, «Модальность» and export
Saving a view · 1 / 6 · More menu

04 Solution

An active view is always visible.

When a view is applied, it appears as a chip above the list with a way to remove it, so it is always clear that the list is not showing everything.

The same view logic works on other layouts, such as the registry shown as a board grouped by counterparty.

Saved view «Просроченные и запланированные» applied: success message, view chip with a remove button, and the status filter set to «Запланирован»
  1. 01

    Confirmation

    Saved and applied, named.

  2. 02

    Active view chip

    Removed with one click.

  3. 03

    Group value

    Switch between status groups.

The payments registry as a board grouped by counterparty
The registry as a board, grouped by counterparty.

05 Key decisions

Key decisions

  1. 01

    Save the current state

    No separate builder: what is on screen is what gets saved.

  2. 02

    Side panel, not a page

    Views are picked while the list stays visible.

  3. 03

    Mine, shared, recommended

    Personal views and views others can use.

  4. 04

    Always show what is applied

    A chip makes a filtered list obvious.

  5. 05

    Empty state teaches

    The empty panel explains how to create the first view.

06 Outcome

What was designed

The flow for creating, saving and applying a modality on a registry, the views panel, a step-by-step wizard variant for adding a modality, and examples on table and board layouts.