openlmis-ref-distro

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
OLMIS-6351: Dropped reference to orderable version from FTAP
OLMIS-6351: Dropped reference to orderable version from FTAP
OLMIS-6351: Update reference data service version

Add OpenLMIS Debezium Kafka Connect Docker image

For project Casper. This is so we do not have to keep building the image on starting up the Casper stack.

    • -0
    • +9
    /reporting/debezium-connect/Dockerfile
    • -0
    • +4
    /reporting/debezium-connect/README.md
Prepared repository for next release

    • -1
    • +1
    /docs/source/components/erd-report.rst
    • -12
    • +12
    /docs/source/components/index.rst
Update documentation to v3.6 versions

To 3.6 versions of documentation, and 3.6 versions of build artifacts.

    • -1
    • +1
    /docs/source/components/erd-report.rst
    • -10
    • +31
    /docs/source/components/index.rst
Updating flow version to 8

This was due to a change in the failure to load the client secrets and I changed the name from Check for Measures to Get Measures so we are able to use the autoload script.

OLMIS-6324 Changing stock filter time range to be Last 3 years

instead of the last 10 days. No results are showing up in the demo data set because the filter is for the last 10 days and no activities have happened in the last 10 days.

Merge pull request #84 from OpenLMIS/update-version

Update generate measures version

Update generate measures version

Merge pull request #83 from OpenLMIS/update-nifi

Update nifi

Remove unnecessary dbdata volume

Update preload script to insert client secret to generate measure reports process group

Updating flow version to 11

This allows us to fix a bug that was found in the merge content processors adding support for requisitions with skipped line items

Merge pull request #82 from OpenLMIS/update-nifi

upgrade nifi from 1.7.0 to 1.9.2

change flow version

Set JVM Memory initial and maximum heap size

Update reference data connector to use replace function instead of escapeJson function

update nifi from 1.7.0 to 1.9.2

Updating the flow version to include fixes

- Fix locations from geographic zones to facilities

- Update the measureReport to include an openlmis RequisitionId

- Removed the process group that restricted measureReports if there were any in the system

- Added a check to see if a measureReport already existed for a requisitionId

update flow version

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?

Change flow version

OLMIS-5584, typos and suggestions from doc review

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?