Hospitality Document Flow
Hospitality reservation status as a free-text field, update behavior, and honesty about missing Submit/Approve Actions menus.
Hospitality Document Flow
Hospitality does not use a typed reservation status enum. ReservationStatus is a string on reservation, guest-room, and room-bill aggregates, updated via UpdateReservationStatus(...).
Hub: Target Document Flow. Overview: Hospitality.
- Active reservation string values (tenant-defined)
- Terminal strings (e.g. cancelled — when used)
Reservation status field
| Fact | Detail |
|---|---|
| Storage | string ReservationStatus on Reservation, ReservationGuestRoom, ReservationRoomBill |
| Update | Domain UpdateReservationStatus(string) |
| Closed enum | None — values are operational strings |
| MudMenu Submit / Approve / Reject | Not implemented for reservations |
Reservation status — free-text field update path
flowchart LR Start((Create)) --> Status[ReservationStatus string] Status -->|Update status| Update[UpdateReservationStatus] Update -->|Refresh| UI[Lists / details refresh] class Start egkStart class Status,Update egkActive class UI egkSuccess
Tenant configuration determines which strings appear (for example confirmed, checked-in, cancelled). This guide does not invent a closed status set.
#Post-action sync
When status strings update through the hospitality UI/API, lists and detail panes reload to show the new value. Failed updates leave the previous string.
#Scenarios
| Scenario | Result |
|---|---|
| Update status string | New value shown after reload |
| Expect ETA Decline Rejection | Not available — ETA only |
| Expect typed enum filter | Not available — free-text field |