| Target release | Release name or number |
|---|---|
| Epic | |
| Document status | |
| Document owner | |
| Technical Lead | Technical Lead who reviews or supports document |
|
Are there any country specific features that should be noted? Who are the personas? Who are the users that will be interacting with this functionality? What are their challenges, responsibilities, and level of connectivity? These personas are intended to be representative archetypes of the key stakeholders who will participate in theses workflows/scenarios.
Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.
| # | Title | User Story | Label | Importance | JIRA Tickets |
|---|---|---|---|---|---|
| 1 | Configure Order File Template | As an implementor, I want to configure the order file template so that my order files are generated with my desired columns and formats to enable transfer of data via an FTP. Acceptance Criteria: See JIRA ticket for more details. | Relevant labels to distinguish source. From which system, or which country? | Must Have | |
| 2 | Configure Order Number for Export | As an implementor, I want to configure how order numbers are generated so that order numbers follow an to match the expected input for the ERP system. Acceptance Criteria: See JIRA ticket for details. | Must Have | ||
| 3 | Configurable FTP or local file folder properties | 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. Acceptance Criteria: See JIRA ticket for details | Must Have | ||
| 4 | Assign supplying depot | As a warehouse clerk, I want to assign a supplying depot to an approved requisition (final state before 'released') so that an order entity can be generated based on the order number template and order file template. Acceptance Criteria: See JIRA ticket for details | Must Have | ||
| 5 | Add Configuration Settings for External Fulfillment | As an implementor, I want to edit fulfillment configuration so that I can manage configuration settings as needed. Acceptance Criteria: See JIRA ticket for details | Must Have | ||
| 6 | View list of approved requisitions | As a warehouse clerk, I want to view the list of approved requisitions so that I can take the steps to convert requisitions to orders. Acceptance Criteria: See JIRA ticket for details | Must Have | ||
| 7 | Notify requisition creator upon convert to order | As the requisition creator I want to receive notification when a requisition is converted to order so I know that the order is being processed. Acceptance Criteria: See JIRA ticket for details | Must Have | ||
| 8 | Transfer Order file via FTP and Error Handling | As a warehouse clerk, I want the order file to transfer via FTP when there are FTP details available for the selected fulfillment warehouse so that the appropriate warehouse receives the orders and can send the correct stock. Acceptance Criteria: See JIRA ticket for details | Must Have | ||
| 9 | Change Order status to Shipped | As a warehouse clerk I want an order status updated so that it reflects that the order has been shipped. Acceptance Criteria: See JIRA ticket for details | Must Have | ||
| 10 | Create a POD from an Order | As OpenLMIS, I want to create and persist a POD populated with the data from the Order so that I can show the POD data to any client that asks for it; for example, the 'manage the POD' screen. Acceptance Criteria: See JIRA ticket for details | Must Have | ||
| Known Bugs |
The following diagram for Fulfillment shows the two business process workflows for Convert to Order and Manage PODs.
Fields | Labels |
|---|---|
| Order Number | Order Number |
| Facility Code | Facility Code |
| Product Code | Product Code |
| Quantity Ordered | Quantity Ordered |
| Pack Size | Pack Size |
Order file is generate with name ‘O’ + order number.csv
Insert the updated Order diagram here
| Fields | Labels | Mandatory? |
|---|---|---|
| Order Number | Order Number | Y |
| Product Code | Product Code | Y |
| Quantity Shipped | Quantity Shipped | Y |
Any file with .csv extension is Picked up for processing from configured folder
Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.
| Description | Link |
|---|---|
| Name of story or release | Link to JIRA |
Initial communication between stakeholders and the development team to help understand scope and estimates.
Below is a list of questions to be addressed as a result of this requirements document:
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 | (e.g. How we make users more aware of this feature?) | Communicate the decision reached | Open, In Progress, Closed, and date of closure |