Use Case Updates

Context

Impact on Existing Use Cases.

The relevant use cases and the impact of this requirement is:

Directly Relevant

Use Case	Impact	Recommended Change
`PRO::OQ::0001` Add Card to Order Queue	The current entry point — this proposal decouples the queue entry so items can be added multiple times, not limited to one card = one queue entry	Add new scenarios where the user can add the same Item or Kanban Card to the Order Queue more than once; each addition creates a separate queue line with its own quantity
`PRO::OQ::0003` View and Filter Order Queue	The queue display will need to show order queue lines instead of (or in addition to) raw Kanban Cards	Update the queue to show order queue lines as the primary rows, with associated Kanban Cards as expandable detail; adjust badge counts to reflect the number of queue lines
`PRO::OQ::0005` Order Queue Grouping Rules	Grouping logic currently keys on cards; would need to account for queue lines as the display unit	Redefine grouping to operate on queue lines; group headers show line count and aggregate quantity rather than card count
`PRO::OQ::0007` Create Order from Queue	The “Create Order” flow currently transitions cards — the relaxed-conditions issue (#808) directly affects the state transitions here	Decouple state transitions from card data-completeness checks; add a user-confirmable override when preconditions are not met so the user can force the transition

Secondarily Relevant

Use Case	Impact	Recommended Change
`PRO::OQ::0004` Queue Aging Visibility	Time-in-state would apply to queue lines, not just cards	Age display reflects when the queue line was created, not when the underlying card last changed state
`PRO::OQ::0006` Inline Vendor Data Completion	Still applies but is triggered from a queue line rather than a card	No structural change; inline completion targets the same ItemSupply record but is initiated from a queue line row
`PRO::PO::0001` Create Purchase Order	PO creation from queue — the API currently requires Kanban Card IDs, but should accept queue lines	Introduce an API endpoint that creates a PO from selected Order Queue lines; existing card-based endpoint remains for backward compatibility
`PRO::PO::0008` Order Data Rules	Line aggregation (`0008::0001`) currently groups by card; queue lines change the aggregation unit	Aggregation groups by Item + UOM from the queue lines; PO line quantity is the sum of queue line quantities, not card reorder quantities

Contextually Relevant

Use Case	Impact	Recommended Change
`PRO::E2E::0001` Order Lifecycle E2E	Full lifecycle verification — state transition relaxation (#808) changes the happy path	Add an alternate E2E path that exercises the override flow when the user advances a queue line despite incomplete data
`PRO::OQ::0002` Inline Field Editing	Data correction at point of use — still applies but the trigger context changes	Inline edits are initiated from a queue line row rather than directly from a card; no change to the underlying ItemSupply update
`PRO::OQ::0003::0006` View Procurement Queue with State Transitions	The sequence diagram shows the current card-based transitions that #808 wants to relax	Update sequence diagram to include an override confirmation step when the system detects unmet preconditions

The two GitHub issues map to these use cases as follows:

#807 (add card multiple times) → PRO::OQ::0001 + the new Demand Item entity from the simplified model
#808 (relax conditions to advance) → PRO::OQ::0007 + PRO::OQ::0003::0006 (the state transition sequences)

Recommended Use Case Additions

New Use Cases

`PRO::OQ::0008` — Order Queue Line Management

The Order Queue currently shows Kanban Cards directly. This use case introduces order queue lines as the unit the user sees and interacts with in the queue, independent of the underlying cards. Addresses #807.

Proposed scenarios:

Add Item to Order Queue from a Kanban Card — the user scans or selects a card and adds it to the queue; a new queue line appears for that Item with the card’s reorder quantity. If the same card or Item is already in the queue, a new line is created rather than rejecting the action.
Add Item to Order Queue directly — the user selects an Item from the Items table and adds it to the Order Queue without needing a depleted Kanban Card as a trigger.
Edit queue line quantity — the user adjusts the quantity on a queue line independently of the card’s reorder quantity, e.g., to order more or fewer units than the card default.
Remove a queue line — the user removes a line from the Order Queue without affecting the state of any associated Kanban Cards.
Merge queue lines — when the same Item appears on multiple queue lines, the user can consolidate them into a single line with summed quantity.

`PRO::OQ::0009` — Override Queue Transition Conditions

The system currently blocks the user from advancing a queue line (e.g., creating an order) when data conditions are not met. This use case adds a user-confirmable override. Addresses #808.

Proposed scenarios:

Advance with incomplete data — e.g., the Item is missing a vendor URL or price. The system shows a warning listing the unmet conditions but lets the user confirm and proceed anyway.
Advance when the card is in an unexpected state — e.g., the card was fulfilled outside the system, or a purchasing transaction was completed offline. The user can acknowledge and force the transition.
Audit trail for overrides — the system records that the transition was forced, by whom, and which conditions were bypassed, supporting traceability and continuous improvement.

New Scenarios on Existing Use Cases

On `PRO::OQ::0001` (Add Card to Order Queue)

Add the same card to the queue a second time — the system creates a new queue line for the same Item rather than rejecting the action as it does today. Addresses #807.
Batch-add multiple cards for the same Item — the system creates one queue line with aggregated quantity from all selected cards, reducing queue clutter.

On `PRO::OQ::0003` (View and Filter Order Queue)

Queue lines with card detail — the queue displays order queue lines as the primary rows; the user can expand a line to see which Kanban Cards are associated with it.
Filter by queue line state vs. card state — these are now independent; the user can filter on either dimension.
Show queue line quantity — display the quantity on each queue line, which may differ from the card’s reorder quantity if the user edited it.

On `PRO::OQ::0007` (Create Order from Queue)

Create order from queue lines — the user selects queue lines (not individual cards) and triggers “Create Order.” PO lines are derived from the selected queue lines.
Partial ordering — the user orders a subset of a queue line’s quantity, and the remainder stays in the queue for a future order.
Override and proceed — when the user triggers “Create Order” and some queue lines have incomplete data, the system shows a confirmation dialog listing the issues and lets the user proceed. Addresses #808.

On `PRO::PO::0001` (Create Purchase Order)

Create PO from Order Queue lines — PO lines aggregate by Item + UOM from the selected queue lines, rather than grouping by card. Requires a new API endpoint alongside the existing card-based one.
Queue lines without cards — when a queue line was created directly from an Item (no card association), the resulting PO line has no servicedCards entries.

Summary of Additions

Proposed Addition	Type	Addresses
`PRO::OQ::0008` Order Queue Line Management	New use case	#807
`PRO::OQ::0009` Override Queue Transition Conditions	New use case	#808
Add same card to queue multiple times	New scenario on `OQ::0001`	#807
Batch-add cards for same Item	New scenario on `OQ::0001`	#807
Queue lines with card detail	New scenario on `OQ::0003`	#807
Create order from queue lines	New scenario on `OQ::0007`	#807
Partial ordering from queue lines	New scenario on `OQ::0007`	#807
Override and proceed	New scenario on `OQ::0007`	#808
Create PO from Order Queue lines	New scenario on `PO::0001`	#807
Queue lines without cards	New scenario on `PO::0001`	#807
Override audit trail	New scenario on `OQ::0009`	#808