...
Administrator sets up order in which a transaction can applied
Actors
- Administrator
Preconditions
Basic Flow
- Administrator edits a properties file with new setting for order of products a transaction import is applied to. The products are listed with commas by short name.
...
FR# | Pri | Description | Comments / Mockups |
---|---|---|---|
3.1 | P1 | M-PESA is an Excel format (97) or CSV in XML format | Is there a way to open the default XML? |
3.2 | P1 | M-PESA import file first few lines contain description of file. These are to be ignored. Only data after row of column headings will be imported in the Transactions section. |
|
3.3 | P1 | Import file will have columns in below table |
|
3.4 | P1 | There will be error checking - to successfully import the data. |
|
3.5 | P1 | If a row contains a cell that's missing a required field, Mifos displays an error message for each row this occurs. |
|
3.6 | P1 | Dates are in the format YYYY-MM-DD HH:MM:ss. If any value under Date column does not start in format of YYYY-MM-DD, then Mifos displays an error message for each row this occurs. |
|
3.8 | P1 | If first value under the Transaction Party Details column does not contain an client Government ID that matches any client in Mifos and/or the next values do not correspond to a Loan Product or Savings Product in Mifos or does not match any open loan account or savings account where a payment/deposit can be applied to the client, or if the default order set in configuration cannot be applied in any way, Mifos throws an error message | See Changes for details |
3.81 | P1 | Check that Status column says "Completed". If it has any other status, Mifos throws the following error message: |
|
3.9 | P1 | Check if the same file name has been imported. If so, then throw an error message and reject the whole import. |
|
3.10 | P1 | After clicking on Continue, Mifos will display the Review & Submit screen with the following: | See 6.5 below for changes |
3.11 | P1 | User can then either
|
|
3.12 | P1 | If User clicks on Submit, Mifos imports the file and displays confirmation screen |
|
3.13 | P1 | There is no option to revert a file upload once it has been submitted. |
|
3.14 | P1 | There is no checking of duplicate rows (see 3.9) |
|
3.15 | P1 | Currency of values imported is directly inherited from the loan product that the loan account is mapped to. |
|
3.16 | P1 | If there are no rows found with import data, the following error message should be thrown: |
|
...
FR# | Pri | Description | Comments / Mockups |
---|---|---|---|
6.1 | P1 | Receipt ID must now be imported and stored in Transaction Details - Receipt ID field |
|
6.2 | P1 | When importing, must check to see if Receipt ID already exists in any transaction in Mifos - if YES, then ignore the row and |
|
6.3 | P1 | Other Party Info must be imported. Take first 10 digits as phone number, and compare with Client's Phone Number fields in Mifos. If there is not a match, then ignore the row and |
|
6.4 | P1 | Changes to Transaction Party Details - no more taking of National ID - remove this functionality. Compare first code listed (before first space) with any loan or savings product in Mifos. If the code exists, import that whole transaction amount to the account associated with that code. Otherwise, ignore what's in the field. |
|
6.5 | P1 | After clicking on Continue, Mifos will display the Review & Submit screen with the following: |
|
Summary after Import - also error log report
...