openlmis-ref-distro

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
typo - integrationTest

typo - integrationTest

OLMIS-6571: Updated README file with step-by-step how to log methods in services and access logs
OLMIS-6571: Updated README file with step-by-step how to log methods in services and access logs
OLMIS-6537 Update reporting documentation
OLMIS-6537 Update reporting documentation
changed notification service version to 4.1.2-SNAPSHOT
changed notification service version to 4.1.2-SNAPSHOT
OLMIS-6413: Use orderable versioning in requisition line items
OLMIS-6413: Use orderable versioning in requisition line items
OLMIS-6351: Dropped reference to orderable version from FTAP
OLMIS-6351: Dropped reference to orderable version from FTAP
Are there other location types that we may need to consider? If so, would we want this description to be more general?

Are there other location types that we may need to consider? If so, would we want this description to be more general?

Geographic

Geographic

Is it likely that an ERP system might be the source of truth for this kind of data, rather than OLMIS? I am thinking of a country that wants to use OpenLMIS primarily for the requisition process bu...

Is it likely that an ERP system might be the source of truth for this kind of data, rather than OLMIS? I am thinking of a country that wants to use OpenLMIS primarily for the requisition process but leverage an existing ERP system for inventory-related processes.

Would OpenLMIS be the source of truth for cce or would a monitoring system like NexLeaf?

Would OpenLMIS be the source of truth for cce or would a monitoring system like NexLeaf?

Is bearer tokens the only method that we want to support?

Is bearer tokens the only method that we want to support?

Also, if you add something about smart endpoints/dump pipes, including some detail about what that means in practice would be helpful as well.

Also, if you add something about smart endpoints/dump pipes, including some detail about what that means in practice would be helpful as well.

I would prefer to lowercase device, so it doesn't get confused with FHIR's Device.

I would prefer to lowercase device, so it doesn't get confused with FHIR's Device.

a part

a part

comes from

comes from

Datetimes

Datetimes

Would you be able to add something in here about smart endpoints and dumb pipes? I think it would be helpful.

Would you be able to add something in here about smart endpoints and dumb pipes? I think it would be helpful.