One authoritative record of an order, not three competing ones.
Status at ebf7cf0: Gap — two order-detail routes and components and three Outstanding pages remain active, and order item responses expose AutoCount account data too broadly.
A permitted user opens an order from any operational or finance list.
| View | Holds |
|---|---|
| Header | The order's identity. Distinguishes operational branch from frozen company/entity. |
| Itemize | The snapshot chain, with a read-only version selector |
| Payments | Every payment row and its verification state |
| Jobs | Every Job Log under this order |
| Refunds | Refund requests and their approval state |
| AutoCount | Posting state, document reference, posting actor and time |
| Activity | The chronological audit trail |
The seven views share one Order identity.
Story. As a permitted user, I want one Order Detail workspace, so that I do not choose between competing records of the same Order.
Acceptance. The seven views share one Order identity and a chronological Activity trail.
Story. As a permitted user, I want a read-only itemize version selector, so that I can inspect Quoted, Technician, OE Review, Verified and Imported history.
Acceptance. The default opens the latest relevant version without mutating history.
Story. As the system, I must hide sensitive AutoCount account numbers from Sales, OE and field users, so that finance-only data is not overexposed.
Acceptance. Response fields follow PBAC and branch scope, not only screen visibility.
Two order-detail routes/components and three Outstanding pages remain active. Order item responses also expose AutoCount account data to general order viewers — a permission gap, not a display gap.
New to these terms? See the Glossary.