On this page

Exploring a process

The process page is the workspace for one log. Its tabs are URL-backed, so any view — a filtered event list, a variant, an activity — is a shareable link.

Process page layout#

The breadcrumb carries the name and the Overview tab opens with the stat strip (format, cases, events, variants, date range, import time); OCEL logs are also badged object-centric. The data tabs — Events, Variants, Activities (or Objects/Events/Relationships on an OCEL log) — stay disabled until the log is ready; Overview and Settings are always available. Banners appear for a mapping that needs review, an import in progress, and a failure.

TabContents
OverviewStat strip, then the module grid with search; disabled cards state their reason.
EventsVirtualised event table with search, per-column filters, sorting, and edit mode.
VariantsAggregated variants: cases, average duration, share of cases, last seen.
ActivitiesActivity list with event counts and editable display names.
SettingsEverything in log settings.

OCEL logs swap the middle tabs for Objects, Events, and Relationships, driven by the log's own Parquet schema.

Events tab#

ControlBehaviour
Cross-column searchDebounced 300 ms.
Missing-values switchShows only rows with empty cells.
Column filtersOperators per column type — string: contains, equals, is_null, is_not_null; numeric, duration, and datetime: equals, gte, lte, is_null, is_not_null; enum and boolean: equals, is_null, is_not_null.
Apply / RestoreCommits the filter to the log (re-running modules), or restores the unfiltered view.
Case chipArriving with ?case_id= restricts the table to that case.
Paging25, 50, 100, or 200 rows.

Variants and activities#

The variants tab filters by activity and minimum case count, sorts by cases, duration, or recency, and shows each variant's share of all cases. Opening a variant gives its sequence, a duration histogram, attribute breakdowns, and the list of its cases. The activities tab lists each activity with its event count and lets you set a display name used across the app.

Cross-module navigation#

Wherever a module renders an activity or a variant, the label links into the matching view, carrying the standard drill parameters (activity, case, variant, object_type, ts_from/ts_to, view, metric; from/to name the two ends of a graph edge). That is what makes a chart a starting point rather than an endpoint.