This was generated by AI during triage.
Split out of #1596 during triage.
Why
The modification endpoint (PA/admin, for APPROVED and WALK_IN bookings) copies all seven *ServiceApproved flags forward unchanged and forces the machine into the Approved state. A service request that was changed during modification keeps its old service decision, and a newly requested service has no decision at all and is never routed to its approvers. Approvers never hear about the change.
Desired behavior
Open questions (to settle at triage)
- What the booking-level state is while a re-routed service is pending. Today modification forces Approved; a pending service may need the booking back in Services Request, or an approved booking with one pending service.
- Whether a newly added service (not previously requested) routes the same way as a changed one.
- Which notification the service approvers receive, and whether the requester is told the service is pending again.
Depends on
Split out of #1596 during triage.
Why
The modification endpoint (PA/admin, for APPROVED and WALK_IN bookings) copies all seven
*ServiceApprovedflags forward unchanged and forces the machine into the Approved state. A service request that was changed during modification keeps its old service decision, and a newly requested service has no decision at all and is never routed to its approvers. Approvers never hear about the change.Desired behavior
Open questions (to settle at triage)
Depends on