-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CFA 2020R4
-
Component/s: None
-
Sprint:CFAMX 2020R4 Sprint 5
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:3
-
Work Type Classification:Sustaining
As a third party system I want to be able to POST a Waste Transaction to InFORM so that I can leverage the inventory management that InFORM offers
Notes
- Note: We do not have any details about the solutions that CFA are planning to implement, other than they would like to use APIs to inject waste, this story is a part of the effort to provide robust, external facing API calls that can be used to GET and POST data.
- Create a streamlined POST that will allow CFA to inject Waste Transactions, containing minimum data required to create a waste transaction
- For example:
- Store Number (not entity id)
- Item Code (not Item Id)
- Unit of measure, depending on unit being wasted:
- Outer - Unit Of Measure
- Inner - Unit Of Measure
- Unit - Unit Of Measure
- Metric Unit - Unit Of Measure
- Quantity of unit being wasted
- Reason Code - By item
- Date & Time of the transaction
Acceptance Criteria
- Confirm that the Request is as streamlined as possible, and only uses data that truly needs to be passed back to InFORM to inject a Waste transaction via the new API calls being developed under this feature
- Confirm that the Store Number must be included in the call
- Confirm that the Store must be Open in order to process the response
- Not Closed or Temporarily Closed
- Confirm that the item being wasted must be InUse/Active in order for the request to complete successfully
- Confirm that the Unit Of Measure passed back is valid for the item being wasted
- Confirm that the quantity being wasted must be a positive value
- Confirm that the quantity being wasted cannot exceed two decimal places
- Confirm that the quantity being wasted cannot exceed 999
- Confirm that a Reason Code is required for each item to be wasted
- Confirm that the Reason Code is Valid in InFORM
- Confirm that the date included cannot be a Sunday
- Confirm that the date included cannot be in the future
- Confirm that the date included cannot be in a closed business period
- Will Englefield to research further
- Confirm that the developer has documented the call in Confluence
- Variable names
- Variable definitions
- Variable usage
- Example Call
- Example response
- See this page for guidance: https://cfacorp.atlassian.net/l/c/yje7GDs6
- implements
-
CFAMX-10366 Make the Waste API robust enough for chain-wide usage by Automated Holding Assistant to inject waste data
- Closed
- is related to
-
CFAMX-11518 2020.R4(S5): Post Waste API - Investigate Posting Items on Sundays
- Done
1.
|
Review Test Scripts | Done | Gareth Leibbrandt (Inactive) |
|
|||||||||
2.
|
Deploy | Done | Unassigned |
|
|||||||||
3.
|
Functional Review with QA | Done | Michael DeBinder (Inactive) |
|
|||||||||
4.
|
DIT | Done | Michael DeBinder (Inactive) |
|
|||||||||
5.
|
Create Test Cases | Done | Soma Dixon (Inactive) |
|
|||||||||
6.
|
Execute Test Cases | Done | Soma Dixon (Inactive) |
|
|||||||||
7.
|
Create endpoint | Done | Michael DeBinder (Inactive) |
|