...
...
...
...
| Warning | ||
|---|---|---|
| ||
This version is not recommended because the Reference Data component contains a bug relating to production database migrations. Use version 3.1.1 instead. |
| Table of Contents |
|---|
Release Notes
...
The OpenLMIS Community is excited to announce the 3.1.0 release of OpenLMIS!
This release represents a significant milestone in the version 3 series, which is the result of a a software re-architecture that allows more functionality to be shared among the community of OpenLMIS users. This version includes a new Stock Management service and also has significant improvements in the Requisition functionality. It also contains contributions from the Malawi implementation, such as a CSV data loading tool for importing reference data (such as facility and product lists) into OpenLMIS.
After 3.1.0 there are further planned milestone releases that will continue towards the vision of providing a full-feature electronic logistics management information system (LMIS) which that ministries of health and organizations can utilize to manage their supply chain. Please reference the Living Product Roadmap for the high-level estimated release schedule for of next feature releases and beyond.Note: Due to a bug in the upgrade from 3.0.0 to 3.0.1, we recommend starting with 3.0.1 or newer. 3.0.1 or newer will upgrade smoothly to 3.1.0.
Background
Download or View on Github
...
- OLMIS-2492: Added new query param to facility search endpoint - code (facility type code)
- Moved warehouse facility type from demo data to initial data.
- OLMIS-2370: Added paginated search orderables endpoint.
- Description field was added to Orderable class.
- OLMIS-2357: Added audit logs for User entity.
- OLMIS-2413: Add spatial data fields into ReferenceData facilities and geo zones
Breaking changes:
- OLMIS-1696: In our medical commodities model, we changed how Orderables, TradeItems and CommodityTypes are associated - both internally to the Reference Data service, but also to external services. Before, the code modeled this relationship as Orderables being an abstract base class to TradeItem and CommodityType. Orderable no longer are abstract, and TradeItem/CommodityType are not inherited, but rather having a "has a" relationship to Orderable.
- CommodityType and TradeItem no longer inherit from Orderable.
- Orderable, TradeItem and CommodityType all migrated to separate tables.
- Orderable is no longer an abstract class - objects may be instantiated from it.
- Orderable accept a map of identifiers where the key of that map is the type of identifier, and the value is the identifier.
- When creating an Orderable, one should give it's identifier in the Orderable's map as e.g. key = commodityType (or tradeItem), value = uuid.
- CommodityTypes is able of having 0 or more Orderables.
- Removed description from CommodityType, added name (string), classificationSystem (string), classificationId (string). All required.
- TradeItem is capable of having 0 or more Orderable.
- Added Dtos for: TradeItem, CommodityType, OrderableDisplayCategory, TradeItemClassification, Dispensable.
- Added get endpoint for retrieve all commoditytypes.
- Added endpoint for create orderables.
- Added pagination for getAll/search endpoints for Orderables, CommodityTypes and TradeItems.
- Added validation for orderable, commodity type and trade item.
- Added data migrations.
- Removed redundant code.
...
Thank you to Team Panda at ThoughtWorks for releasing the first version of the stock management service. Team members included Shiyu JINJin, Deng Yi Deng, Cui PengfeiWei Zhang, Hongwei Peng , and Wei Zhang(Max), Pengfei Cui, Bing Wu.
Thanks to the Malawi implementation team who that has contributed a number of pull requests to add functionality and customization in ways that have contributed global shared benefit:
- <INSERT> the pull request for the bulk uploadsOpenLMIS Reference data seed tool
Also, thanks to everyone who contributed to OpenLMIS 3.0.0.
...