November 17th 2020

Software Development Update

Roadmap: Living Product Roadmap 

Current sprint: 

Upcoming sprint: 

Version 3.10: 

• What to see what is being worked on in this release, please see: https://openlmis.atlassian.net/projects/OLMIS/versions/12817/tab/release-report-all-issues

Team stats: https://openlmis.atlassian.net/secure/Dashboard.jspa?selectPageId=12504

Velocity: 

Open

@Wesley Brown, @Klaudia Pałkowska (Deactivated) (5 min)

Development Update:

Currently on sprint 159

The goal is to release OLMIS 3.10, following the regular release checklist;

Automated testing will focus on automating the verification of system performance after a new release

Proposed Feature Contribution: R&R Rejection Reason

Proposed by OLMIS-TZ, as a R&R is rejected, the user has the capability to select a reason why. The reasons are configurable. The reasons will also be available on the notifications sent to users as well as on the reporting platform.

@Dércio Duvane: Are these reasons related to the ones already available under Stock Management?
@Wesley Brown: These are configured separately therefore probably there wouldn't be a shared config.

Proposed Feature Contribution: Google Analytics Support

@Sebastian Brudziński: How is this different from the current Google Analytics support?

The current support already tracks the navigability on OpenLMIS. These functionalities are hard to find on confluence, therefore, the new feature;

SolDevelo team to look for the feature documentation and current implementations...

@Christine Lenihan: As we research it might be good to take a look at what we might be able to do with the information

Proposed SIGLUS Feature Contributions

Presentation that describes features:

Partial Fulfillment

• Christine - What happens with the sub-orders over time? Do they expire? What happens if they don't get fulfilled by the next order?

  • This seems to be not completely defined

  • Christine - This could lead to confusion if things get out of hand. We may want to figure out what our best practice is here

  • Dercio - Setting the Fill Qty to zero does move the order to the next stage

• Sebastian - Does each sub-order have it's own PoD?

  • Dercio - Each is a separate PoD

  • Sebastian - PoD's feed back into the requisition for the next period and this relationship would need to be considered for sub-orders

• Sebastian - How does this affect reporting?

Stock Card Overview

• Wes - Is the lot code visible anywhere on stock card overview?

  • Momad - Yes, in the current version it is visible

Requisition Configuration

• Wes - Are Sections configurable?

  • Dercio - Not configurable and would required metadata 

• Sebastian - This links to the Program Data feature that was part of the Gap project

• Wes - This would require some significant work to be able to incorporate into core

Notification Center

• Sebastian - different than our current notifications (messages), this is more action-related. We might be able to reuse the same ui though.

• Wes - Is the list of notifications events configurable? 

  • Dercio - No, the event triggers are hardcoded

  • Wes - This would likely need to be configurable to be incorporated into core

Next PC meeting: Topic ideas??

1. Get feedback on the possibility of incorporating the TZ Budget and Distributed Lot Mgmt features into the ref-distro.

2. ? @Sachin Jagtap (Unlicensed) to give an update on GAVI/WHO work regarding COVID Vaccine Distribution (in the future)

3. ? Updates to the SIGLUS Mobile App, what are the goals for this?

Additional Requests and Information: