Configurable FTP or local file folder properties

Description

As an implementor, I want to set up the transfer properties (either FTP or local folder) by facility so that I can transfer order files via FTP/local folder for external fulfillment. In the end, the file will be consumed by an external ERP system.

FTP or local folder credentials must be specified for each warehouse that has been named in a supply line, so that OpenLMIS knows where to route each approved order.
Additional details:

Background taken from the Configuration Guide
Each Supply Line we created in Step #8 includes a designated warehouse that will fill orders for a particular program. OpenLMIS relies on FTP data transfers to forward orders to these warehouse(s). Typically, there will be an FTP server associated with the ERP system used to manage the warehouse. FTP credentials must be specified for each warehouse that has been named in a supply line, so that OpenLMIS knows where to route each approved order.
In some cases, an organization may run multiple warehouses with a single ERP system

The FTP credentials must be still be specified for each warehouse, even if the FTP credentials are identical for each warehouse in this "shared" environment. In other cases, an organization may run multiple warehouses with the same ERP system, but may set up individual file directories on their FTP server, for orders that are sent to the each of the warehouses. The FTP details upload supports this scenario.

Acceptance Criteria for FTP

  • ability to set up FTP details for a facility/supplying depot:

    • FTP server host,

    • FTP server port ,

    • FTP server authentication username,

    • FTP server authentication password,

    • FTP local folder path

  • the FTP details are tied to a facility by facility code

Acceptance Criteria for Local folder

  • ability to set up local details for a facility/supplying depot:

    • path to local directory,

  • the local details are tied to a facility by facility code

Attachments

7

is blocked by

QAlity Plus - Test Management

Checklists

Activity

Lucyna Laska 
December 20, 2016 at 7:45 AM

When I set up the transfer properties (either FTP or local folder) by facility, I can transfer order files via FTP/local folder. All works.

More details in test case: https://openlmis.atlassian.net/wiki/display/OP/829%3A+Configurable+FTP+or+local+file+folder+properties

Lucyna Laska 
December 19, 2016 at 10:08 AM

, Ok, thanks for confirmation and explanation.

Łukasz Lewczyński 
December 19, 2016 at 10:06 AM


1. Unfortunately Yes
2. If you start blue you have to define volumes in the blue compose file because it does not see a fulfillment compose file (I am not docker expert so maybe this is incorrectly explanation)

Lucyna Laska 
December 19, 2016 at 9:58 AM

Questions for you:
1. When I update my requisition and:

  • type is not changed (e.g. I modify the path), the ID of my transferProperties configuration is still the same

  • type has been modified (at the beginning I set local), the ID of my transferProperties is changed. Of course, the previously configuration is deleted. This behavior is expected?

2. When I created the local configuration, I converted my requisition to order and the CSV file was not created. I had to add the volume to docker-compose.yml but in blue service (despite that this volume is already added in docker-compose.yml at fulfillment service). Could you explain why I had to do that?

Łukasz Lewczyński 
December 16, 2016 at 10:09 AM

If you modify the docker-compose.yml and add additional volume I think it should work.

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Story Points

Original estimate

Time tracking

4d 4h logged

Components

Sprint

Fix versions

Priority

Time Assistant

Created July 11, 2016 at 9:22 PM
Updated June 22, 2017 at 9:01 PM
Resolved December 20, 2016 at 7:46 AM