Update Count API

1. Implement min/max ranges for count quantities, precision of 2 (round if we aren't already)
2. 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...)
3. Make sure all the methods in the API have the correct permission restrictions (any additional security we want to add?)
4. 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)
5. Make sure apply date & time is in the past
6. Do we need to flag counts older than two days, or warn if there are open orders or transfers?
7. Ensure that API Calls are created in Katalon to test this

Point to think about, no action required

1. Modify API methods to accept store number instead of entity id
   • Lets keep with using a single API call to get the entity id up front, until such times that CFA ask for something else
2. Make Order API more consistent - (An an example, with counts sometimes we use CountType as an int, sometimes a string, sometimes it's called "StockCountType")
   • This would involve a potential refactor of pages
3. Consider throttling usage so an outside process can't perform an attack through a massive volume of transactions
   • Adding a spike for this, maybe some sort of API gateway?