-
Type: Story
-
Status: Open (View Workflow)
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Work Type Classification:Sustaining
Story
As a user, I would like to be able to set and get waste values via an API. This will help me to track these more easily.
API Params
- Store
- Date
- Time
- Outer
- Inner
- Unit
- Reason (Data validated list)
- Favorite (yes/no)
Open Questions
- The "Reason" is data validated in the UI with a dropdown menu. How should the API handle this?
- What parameters am I missing?
UAC
Confirm
- The user can get data using the waste API
- Waste updates made in the UI are available to the user via get
- The user can post data using the waste API
- The waste history is updated in the UI when a waste item is posted via the API
- implements
-
CFAMX-10712 Waste API - Create API to support the creation of a Waste Adjustment
- Closed
1.
|
Review Test Scripts | Ready for QA | Unassigned |
|
|||||||
2.
|
Deploy | Ready for QA | Unassigned |
|
|||||||
3.
|
Functional Review with QA | Ready for Developer | Unassigned |
|
|||||||
4.
|
DIT | Ready for Developer | Unassigned |
|