ExtraUpdateRequestedEvent

EventType: EXTRA_UPDATE_REQUESTEDDomain: admin Broker subject: —

Stores arbitrary extra data on a job or work order document without going through the standard production event flow. Used for operator-assisted data corrections or custom field updates that do not map to a domain event.

No broker notification

ExtraUpdateRequestedEvent extends BaseAdmin, which itself extends BaseProductionEvent. However, ExtraUpdateRequestedEvent does not set _notification_subtopic, so no broker message is published after commit.

Trigger

Triggered by: POST /event (universal event dispatcher)

Dispatched via POST /event in backend/api/endpoints/traceability.py with event_type: EXTRA_UPDATE_REQUESTED.

Preconditions

• Entity identified by info.entity_type + info.entity_key exists

State Changes (Transaction)

Collections: Job, WorkOrder

• Target document (Job or WorkOrder) updated: extra field set to info.extra_data

Side Effects (post_processing)

Extends BaseAdmin.post_processing():

• Calls update_work_order()
• Sets job.forced = event_key
• No broker publish (no _notification_subtopic)

InfoModel Fields

Field	Type	Description
entity_type	Literal['job', 'work_order']	Type of entity to update
entity_key	str	ArangoDB key of the entity
extra_data	Any	Arbitrary data to store in the extra field
job_key	str | None	Job key (for post_processing context)
work_order_key	str | None	Work order key (for post_processing context)

Related Events

None.

Source

ExtraUpdateRequestedEvent on GitHub