4pm-5pm PDT
https://www.uberconference.com/richmagnuson
IP audio, or Dial-in: 1-716-293-9263, meeting PIN: 60307
Time | Item | Who | Notes |
---|---|---|---|
5min | Agenda item | Name |
|
A productive discussion on Extensiblity, Beta and our current plan for a useful extension example occurred. Out of that discussion Elias shared a real scenario to ask how these mechanisms and the community would be utilized to avoid a fork. The scenario:
There are two organizations supplying commodities in country: MSL (ministry) and CHAZ (charity). Of these most of the commodities in a requisition will be supplied through MSL. However for a few of these commodities (5-6), and only at some facilities in the country, CHAZ will actually supply those commodities. The requisitioning facility will fill out one Requisition and submit it and have it authorized. When the district supervisor goes to approve it however, they will essentially be creating two orders: 1 for MSL which will fulfill the regular commodities, and 1 for CHAZ which will fulfill just a few of the commodities.
This workflow introduces a number of important changes:
the concept of a Supplying Partner is introduced to distinguish MSL supply lines and commodities from CHAZ supply lines and commodities.
an Approver would want to see in the UI what quantities they we're approving based on the Supplying Partner that will fulfill them
an Approver is essentially creating not 1 order, but potentially many (or 2 in this case)
In briefly discussing how the mechanisms would apply, we thought:
How this is actually addressed should be fleshed out and discussed in future meetings.