Josh's thoughts and questions:
Decision: bring to PC. Get decisions on the above questions. Share with team and start designing.
Read API will be done first.
Questions: Should the write API support batch and individual sign in creation?
Decision: Need further discussion on the configuration of Sources/Destinations. How does a facility know who their valid sources and destinations? We should review and look into supply lines within requisitions. We know the hierarchy will be different than requisitions.
Approach: VR suggests creating the write API while doing the read API, however leave out the business logic and outline all the questions to be addressed for configuring the new facilities.
|20 min||Open questions|
|5 min||New QA onboard|
- Shiyu Jin (Deactivated), when making stories, please make sure to add the component "Stock Management". Also, let's make sure each story has a fix version indicating the desired release date. Thanks.
- Shiyu Jin (Deactivated) send an email to Mary Jo Kochendorfer (Deactivated) with possible cases and raise the question to the PC, whether we should allow negative SOH, how long, how to configure and how to design the process
Shiyu Jin (Deactivated) create a ticket for the configuration source/destination process
- Shiyu Jin (Deactivated) cover the permission management in-depth discussion during the inception in Seattle