Daily Closing Schema
Felder
Daily Closing Schema
Persistent confirmation that a user has reviewed and closed their workday. Captures guard results, override reasons, and is automatically superseded when post-close changes happen.
userId
User who owns this daily closing
date
Date of the daily closing (ISO YYYY-MM-DD, tenant-local time)
orgUnitId
Org unit (team) this closing belongs to at closing time. Nullable for tenants without formal org structure.
policyId
Effective policy that governed this closing
closedAt
Timestamp when the day was closed
guardResults
Snapshot of guard evaluations at closing time
overrides
Guards that the user closed with a reason override
notes
Snapshot of the daily_note content as of closing time; subsequent edits on the daily_note do not change this field
recapId
FK to daily_overview_recaps if a self-scope recap was generated for this date
supersededAt
Set when a post-close mutation (time_record/phone_call/remote_session/calendar_event) invalidates this closing; user must create a fresh closing
supersededBy
time_record_changephone_call_changeremote_session_changecalendar_event_changemanualsupersededRefId
ID of the entity whose change triggered the supersede
Keine Felder passen zum Filter.
Standard-Endpoints
Diese Resource folgt dem generischen CRUD-Vertrag der Plattform. Lesen Sie die Konventionen für Pagination, Idempotenz, Optimistic Locking und Audit. Die wichtigsten Endpoints:
GET /api/v1/daily_closings— Liste, paginiert + filterbarGET /api/v1/daily_closings/<id>— Einzelne EntityPOST /api/v1/daily_closings— AnlegenPATCH /api/v1/daily_closings/<id>— Teil-UpdateDELETE /api/v1/daily_closings/<id>— Soft-DeleteGET /api/v1/daily_closings/<id>/timeline— Audit + Aktivitäten