BusinessPad

Selected UX case · Уведомления

Notifications

A notification centre for a system where many things change at once: grouped by where the change happened, with the change itself shown on the card.

Notifications for one process instance with an Events toggle, showing stage changes and new documents

01 Context

Every process produces events.

Stages change, responsible people are reassigned, documents and counterparties are added, comments are left. Each of these can matter to someone working on the process.

Notifications collect them in one place, reachable from the main navigation.

02 Problem

A long list of “something changed”.

With many processes running, a single feed fills quickly, and a title alone does not say whether a notification needs attention. Opening each one to find out is slow.

03 Design approach

Group by source. Show the change on the card.

Notifications are grouped by where they came from: favourites, process instances, business processes, company, and all. Business process notifications have their own categories, from tasks and finance to goods.

Each card names the event, the process instance, and the change itself, such as the old and new stage, the new responsible person or the attached document.

Notifications page on Favourites: cards for a new responsible person, a stage change, a new document and a new counterparty, each with the process instance, the change, author, time and a «Прочитать» button
  1. 01

    Grouped by source

    Each group shows how many are new.

  2. 02

    The change itself

    From stage → to stage.

  3. 03

    Who and when

  4. 04

    Add to favourites

  5. 05

    Mark as read

04 Solution

From all notifications to one instance.

From a notification, the user can open everything that happened in that process instance. A breadcrumb leads back, and an Events toggle narrows the list.

Business process notifications open as a second-level menu of categories, each with its own count.

Notifications page on Favourites: cards for a new responsible person, a stage change, a new document and a new counterparty, each with the process instance, the change, author, time and a «Прочитать» button
Narrowing down · 1 / 5 · Favourites

05 Key decisions

Key decisions

  1. 01

    Source first

    Grouping by where a change happened, not by date alone.

  2. 02

    Content on the card

    The change is readable without opening anything.

  3. 03

    Favourites

    Important notifications can be kept at the top.

  4. 04

    Drill into an instance

    All events of one process instance, with a way back.

06 Outcome

What was designed

The notifications page with source groups and business process categories, card layouts for each event type (responsible person, stage, document, counterparty, comment), and the drill-down into a single process instance.