Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
ACQ Sprint 55, ACQ Sprint 56
-
3
-
Thunderjet
Description
In most cases the users will be perfectly happy with an automatically generated/assigned po_number, but in some cases they may want/need to specify one when creating an order. In order to accommodate both, we should populate the po_number field with an auto-generated value obtained from mod-orders. If the user decides to supply their own value instead, we need to verify that the value provide is valid (adheres to the prescribed format) and is unique. This validation can be done via mod-orders.
GET /po_number can be used to obtain a auto-generated po_number. See MODORDERS-87 for details.
POST /po_number can be used to validate a user-specified po_number. See MODORDERS-89 for details.
When validating a po_number, the entire po_number should be supplied, including the optional prefix and suffix.
TestRail: Results
Attachments
Issue Links
- is blocked by
-
MODORDERS-87
Create GET /orders/po_number endpoint for generating a po_number
-
- Closed
-
-
MODORDERS-89
Create POST /orders/po-number/validate endpoint for validating a po_number
-
- Closed
-
- relates to
-
UIOR-114
Purchase Order: Recall PO Number
-
- Closed
-
-
UXPROD-1388 Create New Purchase Order Lines
-
- Closed
-
-
MODORDERS-146
Return application/json (error schema) for all errors
-
- Closed
-