You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The process instance history view has no chronological record of all executed elements — there is no table showing which activities (start events, service tasks, user tasks, gateways, end events, …) ran, in which order, with which timestamps.
Current state
No component fetches GET /history/activity-instance anywhere in the codebase.
The closest existing tab, "User Tasks", queries the runtime task list only (GET /task?processInstanceId={id} via get_process_instance_tasks) — completed tasks never appear, and for finished instances the tab is permanently empty. Historic sources (/history/task, /history/activity-instance) are unused.
Expected (C7 Cockpit parity)
In history mode, a chronological activity table for the instance: activity name, activity type, start time, end time, duration, canceled marker — sourced from
GET /history/activity-instance?processInstanceId={id}&sortBy=startTime&sortOrder=asc
This is the same data source needed for the historic diagram badges (#99) — one new history resource function + signal serves both.
Suggested implementation
history.activity_instance.by_process_instance resource function + signal in state.js.
Optionally enrich the User Tasks tab with historic task details (assignee, due date via /history/task) as a separate step — the activity table above already covers the "what ran when" question for all element types.
Summary
The process instance history view has no chronological record of all executed elements — there is no table showing which activities (start events, service tasks, user tasks, gateways, end events, …) ran, in which order, with which timestamps.
Current state
GET /history/activity-instanceanywhere in the codebase.GET /task?processInstanceId={id}viaget_process_instance_tasks) — completed tasks never appear, and for finished instances the tab is permanently empty. Historic sources (/history/task,/history/activity-instance) are unused.Expected (C7 Cockpit parity)
In history mode, a chronological activity table for the instance: activity name, activity type, start time, end time, duration, canceled marker — sourced from
This is the same data source needed for the historic diagram badges (#99) — one new history resource function + signal serves both.
Suggested implementation
history.activity_instance.by_process_instanceresource function + signal instate.js.<time>like the existing tables; activity names come directly from the REST payload (activityName), no BPMN mapping needed./history/task) as a separate step — the activity table above already covers the "what ran when" question for all element types.