...
IP audio, or Dial-in: 1-716-293-9263, meeting PIN: 60307
Notes
...
rest-api endpoints in v2 (for zambia & elmis fac edition) - implemented a field for which application is accessing the api. === With our services we may want some analytics on who (application/user/...) is using the service.R&R process: each endpoint.
Elias points out that in 2.0 feature for skipping line items from previous period (that were skipped). Named a feature was added called "hide skipped line items". So in first initiation, they add the products they normally want to use. Rationale is that screen should match paper form (original reasoning), however some health posts (TZ) hadn't had a paper form before, so the 200+ products were overkill as they hadn't had a paper form before to match from. Didn't use facility type workaround as health post to health post had variability. So simpler to just have them choose the products they normal see from the pre-aproved listproducts" that was a configuration option on the Requisition Template. When checked, when a Requisition was first initiated (as in first time ever for that facility), the user would manually select which products they wanted on their Requisition from the list of full-supply products. Going forward, the user would only see the Product's they initially selected ( Elias Muluneh could they ever add/sub after the initial selection?) and not the full list of full supply approved products, this made it cleaner and simpler to order what they typically ordered. The rationale for this was that some facilities (health posts in TZ) never had used the paper R&R forms and so the screen had no need to match it exactly. The facilities also had a much smaller list of product's that they typically ordered and that list wasn't common enough amoung all these facilities to create custom Facility Approved Product lists for each one.
Goals
- Discuss Beta release. Beta is the end of October '16, this is the second to last call before that release
- Community updates
...