Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
ACQ Sprint 54, ACQ Sprint 55, ACQ Sprint 56
-
3
-
Thunderjet
Description
In order to centralize po_number generation, but still allow the UI to suggest a value, we need an API endpoint that returns a generated po_number.
po_number generation is already happening in mod-orders (PostOrdersHelper), so that code can be refactored for use here. The current implementation can be scrapped and replaced with a call to the new GET /orders-storage/po_number endpoint. Later we may add a prefix and/or suffix to the value obtained, but that's beyond the scope of this story.
Acceptance Criteria:
- GET /orders/po_number is defined (e.g. in RAML/ModuleDescriptor) and implemented (code and schema)
- returns an appliacation/json response with a single field "po_number" (status 200)
- Unit tests
TestRail: Results
Attachments
Issue Links
- blocks
-
MODORDERS-107
API Tests for GET /po_number
-
- Closed
-
-
UIOR-71
Adjustments to po_number field on create/edit order forms
-
- Closed
-
- is blocked by
-
MODORDERS-123
Orders and PO Lines endpoints restructure
-
- Closed
-
-
MODORDSTOR-33
Create GET /orders-storage/po_number
-
- Closed
-
- relates to
-
MODORDERS-88
Honor po_number if passed in during order placement.
-
- Closed
-
-
MODORDERS-89
Create POST /orders/po-number/validate endpoint for validating a po_number
-
- Closed
-
-
UIOR-77
Order Settings: Purchase Order Number
-
- Closed
-
-
UXPROD-1388 Create New Purchase Order Lines
-
- Closed
-