What must be complete before an order or a planned assignment goes live.
Status at ebf7cf0: Aligned — backend validation and per-row readiness are implemented.
Drafts may be incomplete. Dispatch is the hard gate. This is the one place where the system refuses to move forward.
Sales dispatches an Order, or OE commits a planned assignment.
Sales dispatch requires: branch · customer · service address · service type · Source of Order · salesperson · at least one item · and a Job Log with date and slot.
OE commit revalidates the operational fields for every draft before applying any assignment.
Story. As OE, I want incomplete drafts to show what is missing, so that I can return them for completion.
Acceptance. Each row identifies missing customer, address, branch, service type, Source of Order, salesperson, item, date or slot as applicable.
Story. As OE, I want one Update action to commit only a fully valid planning batch, so that the live schedule cannot be partially changed.
Acceptance. If one draft fails validation, none of the drafts in that commit are applied.
Story. As the system, I must enforce the gate server side, so that UI or automation cannot bypass it.
Acceptance. Invalid dispatch requests return structured missing-field errors and make no live assignment changes.
Backend validation and per-row readiness are implemented and substantially aligned. The separate company-freeze timing gap belongs to Order intake and Account posting, not here.
New to these terms? See the Glossary.