-
Type:
Feature Request
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: CFA 2020R1
-
Component/s: API
-
Labels:
-
Links:
This feature is an output of the requests to provide direct integration to InFORM via API, allowing CFA to build apps for specific tasks
APIs documented
- Order -
CFAMX-5976 - Count -
CFAMX-5967 - Adjustments -
CFAMX-6078
The following was documented by David based on investigation into the Count API
From CFAMX-5967
- Implement min/max ranges for count quantities, precision of 2 (round if we aren't already)
- Ensure API error messages are informative when possible (no such store, invalid count Id, count value outside of range, no such location, invalid unit for item, etc...)
- Modify API methods to accept store number instead of entity id
- Make sure all the methods in the API have the correct permission restrictions (any additional security we want to add?)
- Make sure that user not only has permission to perform a count, but also is assigned to the store being counted (we probably don't check this since our UI does it for us)
- Make sure apply date & time is in the past
- Do we need to flag counts older than two days, or warn if there are open orders or transfers?
- Make Count API more consistent - (sometimes we use CountType as an int, sometimes a string, sometimes it's called "StockCountType")
- Consider throttling usage so an outside process can't perform an attack through a massive volume of transactions
New Swagger endpoint: https://m.inform.jatesting.cfahome.com/swagger/docs/v1
- is implemented by
-
CFAMX-6941 Updates to Order API
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed