uslimato
|

Lifecycle Kanban

Overview

The Lifecycle page (/lifecycle) shows all asset movements as a kanban board with three fixed columns:

  • In progress — active movements
  • Completed — movements that ran through successfully (including applied field bindings)
  • Cancelled — stopped early

Each card shows the movement number, process name, asset count, starter, and start date. Clicking a card opens the detail page at /movements/:id.

Filters

Above the board two filters are available — both act purely client-side on the loaded movement list.

FilterBehaviour
Asset typeDropdown with all asset types in the tenant. Shows only movements that contain at least one asset of the chosen type.
SearchFree text — filters cards by movement number or process name (case-insensitive).

A "Clear filters" button appears as soon as at least one filter is active.

Drag & Drop (admin / processes:manage)

Users with the processes:manage permission (or admin) can drag cards out of the In progress column into Completed or Cancelled. No other column moves or backwards moves are permitted.

UI details:

  • Only cards with status in_progress are draggable — everything else is a plain link.
  • Drops from other tabs or external applications are ignored.
  • Drops apply an optimistic UI update (the card moves columns immediately).
  • On backend failure the UI reverts and a toast surfaces the error.
  • Users without the permission see the board in static link-only mode — no drag is initiated.

Status Transition Rules

The following rules apply to drag-and-drop status changes:

  • Allowed transitions: In progress → Completed and In progress → Cancelled.
  • Any other transition is rejected.
  • Required permission: processes:manage (admins have access automatically).
  • On Completed:
    • All linked process steps are marked as completed.
    • If the process defines field bindings (e.g. assignment, location), they are applied to the involved assets.
    • The process' target status is applied to all involved assets.
  • On Cancelled: the movement and all related process steps are marked as cancelled.
  • All status changes are recorded in the audit log.

Security

  • All write operations are tenant-isolated.
  • User and location assignments are validated against the tenant's own data before being applied — invalid references are silently skipped.
  • Only data that already exists within the tenant is processed — cross-tenant access is impossible.

Related topics