Events Reference

Every state change in the Progress Platform that requires post-commit side effects flows through a typed Event object. Events are applied within an ArangoDB transaction and, on commit, publish notifications via broker subjects (consumed by the SSE stream and the Sparkplug bridge).

The catalogue below is auto-extracted from backend/api/events/ on every push to DEV. The top-10 events have hand-crafted sequence diagrams; the remainder ship with auto-extracted InfoModel and post-processing summaries (suitable for catalogue navigation, not deep-dive walkthroughs).

Quick navigation by domain

• Production — 14 events
• Inventory — 18 events
• Serial — 6 events
• Collaboration — 13 events
• Admin — 1 event
• WIP — 4 events
• Work Session — 3 events

Full event index

Event	Domain	EventType	Broker Subject
ExtraUpdateRequestedEvent	admin	EXTRA_UPDATE_REQUESTED	—
IssueClosedEvent	collaboration	ISSUE_CLOSED	progress.notification.issue
IssueCreatedEvent	collaboration	ISSUE_CREATED	progress.notification.issue
IssueDeletedEvent	collaboration	ISSUE_DELETED	progress.notification.issue
IssueReopenedEvent	collaboration	ISSUE_REOPENED	progress.notification.issue
IssueUpdatedEvent	collaboration	ISSUE_UPDATED	progress.notification.issue
MessageDeletedEvent	collaboration	MESSAGE_DELETED	progress.notification.message
MessagePostedEvent	collaboration	MESSAGE_POSTED	progress.notification.message
MessageUpdatedEvent	collaboration	MESSAGE_UPDATED	progress.notification.message
TaskCanceledEvent	collaboration	TASK_CANCELED	progress.notification.task
TaskCompletedEvent	collaboration	TASK_COMPLETED	progress.notification.task
TaskCreatedEvent	collaboration	TASK_CREATED	progress.notification.task
TaskLinkedEvent	collaboration	TASK_LINKED	progress.notification.task
TaskReopenedEvent	collaboration	TASK_REOPENED	progress.notification.task
TaskSuspendedEvent	collaboration	TASK_SUSPENDED	progress.notification.task
TaskUnlinkedEvent	collaboration	TASK_UNLINKED	progress.notification.task
TaskUpdatedEvent	collaboration	TASK_UPDATED	progress.notification.user.{user_key}
AssignmentCompletedEvent	inventory	ASSIGNMENT_COMPLETED	progress.notification.inventory
AssignmentStartedEvent	inventory	ASSIGNMENT_STARTED	progress.notification.inventory
CountAppliedEvent	inventory	COUNT_APPLIED	progress.notification.inventory
CountCanceledEvent	inventory	COUNT_CANCELED	progress.notification.inventory
CountCompletedEvent	inventory	COUNT_COMPLETED	progress.notification.inventory
CountDiscardedEvent	inventory	COUNT_DISCARDED	progress.notification.inventory
CountImportedEvent	inventory	COUNT_IMPORTED	progress.notification.inventory
CountSessionAppliedEvent	inventory	COUNT_SESSION_APPLIED	—
CountSessionCompletedEvent	inventory	COUNT_SESSION_COMPLETED	progress.notification.inventory
CountSessionConfirmedEvent	inventory	COUNT_SESSION_CONFIRMED	progress.notification.inventory
CountSessionResumedEvent	inventory	COUNT_SESSION_RESUMED	progress.notification.inventory
CountSessionStartedEvent	inventory	COUNT_SESSION_STARTED	progress.notification.inventory
CountStartedEvent	inventory	COUNT_STARTED	progress.notification.inventory
InventoryChangedEvent	inventory	INVENTORY_CHANGED	progress.notification.inventory
MovementCompletedEvent	inventory	MOVEMENT_COMPLETED	progress.notification.inventory
MovementPlannedEvent	inventory	MOVEMENT_PLANNED	progress.notification.inventory
MovementReversedEvent	inventory	MOVEMENT_REVERSED	progress.notification.inventory
MovementUpdatedEvent	inventory	MOVEMENT_UPDATED	progress.notification.inventory
PositionConfirmedEmptyEvent	inventory	POSITION_CONFIRMED_EMPTY	progress.notification.inventory
WarehouseListClosed	inventory	WAREHOUSE_LIST_CLOSED	progress.notification.inventory
ActiveBatchChangedEvent	production	ACTIVE_BATCH_CHANGED	progress.notification.production
BatchCompletedEvent	production	BATCH_COMPLETED	progress.notification.production
BatchCreatedEvent	production	BATCH_CREATED	progress.notification.production
BatchReleasedEvent	production	BATCH_RELEASED	progress.notification.production
JobBackOnlineEvent	production	JOB_BACK_ONLINE	progress.notification.production
JobPauseForcedEvent	production	JOB_PAUSE_FORCED	progress.notification.production
JobPausedEvent	production	JOB_PAUSED	progress.notification.production
JobPausedOfflineEvent	production	JOB_PAUSED_OFFLINE	progress.notification.production
JobResumedEvent	production	JOB_RESUMED	progress.notification.production
JobStartedEvent	production	JOB_STARTED	progress.notification.production
QueueUpdatedEvent	production	QUEUE_UPDATED	progress.notification.production
StepCompletedEvent	production	STEP_COMPLETED	progress.notification.production
StepEditedEvent	production	STEP_EDITED	progress.notification.production
WorkOrderStartedEvent	production	WORK_ORDER_STARTED	progress.notification.production
SerialCreatedEvent	serial	SERIAL_CREATED	progress.notification.serial
SerialDeletedEvent	serial	SERIAL_DELETED	progress.notification.serial
SerialLinkedEvent	serial	SERIAL_LINKED	progress.notification.serial
SerialReleasedEvent	serial	SERIAL_RELEASED	progress.notification.serial
SerialUnlinkedEvent	serial	SERIAL_UNLINKED	progress.notification.serial
SerialUpdatedEvent	serial	SERIAL_UPDATED	progress.notification.serial
WIPBookedEvent	wip	WIP_BOOKED	progress.notification.production
WIPDeclaredEvent	wip	WIP_DECLARED	progress.notification.production
WIPRemovedEvent	wip	WIP_REMOVED	progress.notification.production
WIPUnbookedEvent	wip	WIP_UNBOOKED	progress.notification.production
WorkSessionCanceledEvent	work_session	WORK_SESSION_CANCELED	progress.notification.production
WorkSessionClosedEvent	work_session	WORK_SESSION_CLOSED	progress.notification.production
WorkSessionCreatedEvent	work_session	WORK_SESSION_CREATED	progress.notification.production

NATS subject taxonomy: Production / Inventory / Serial / Issue / Task / Message subtopics map to progress.notification.<subtopic>. The Sparkplug bridge consumes a subset of these for upstream MES integrations — see ADR-0002 in the Sparkplug demo workstream for the locked taxonomy.

Events with NATS Subject — do not publish a notification on commit. CountSessionAppliedEvent extends BaseEvent directly (bypassing BaseInventoryEvent) so its _notification_subtopic is null — downstream consumers re-read canonical session state after async processing completes. ExtraUpdateRequestedEvent (admin) similarly has no subtopic override on its base class.