[
http://mifosforge.jira.com/browse/MIFOS-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59658#action_59658
]
Mifos Hudson Jira Plugin User commented on MIFOS-3215:
------------------------------------------------------
Integrated in !http://ci.mifos.org/hudson/images/16x16/blue.gif! [head-master
#1829|http://ci.mifos.org/hudson/job/head-master/1829/]
FIXED MIFOS-3215 Integrated patch to address this issue.
Van Mittal-Henkle :
[5b85921a6680749ca5d0a8aac1611658486c2b26|http://mifos.git.sourceforge.net/git/gitweb.cgi?p=mifos/head&a=commit&h=5b85921a6680749ca5d0a8aac1611658486c2b26]
Files :
*
application/src/test/java/org/mifos/accounts/api/StandardAccountServiceIntegrationTest.java
* application/src/main/java/org/mifos/accounts/api/StandardAccountService.java
* api/src/main/java/org/mifos/accounts/api/AccountService.java
> Review API addition to allow plugins to detect duplicate payment info
> ---------------------------------------------------------------------
>
> Key: MIFOS-3215
> URL: http://mifosforge.jira.com/browse/MIFOS-3215
> Project: mifos
> Issue Type: Improvement
> Reporter: Sam Birney
> Assignee: Van Mittal-Henkle
> Priority: Major
> Attachments: AudiBankXlsImporter.java, AudiBankXlsImporterTest.java,
> patch-3215.txt
>
>
> the AccountService API currently provides a useful way for client code to
> apply payments to accounts, which is used by the bank import (and MPesa
> import) plugins.
> I propose enhancing it with a way to provide information about existing
> payments as well. With the ability to retrieve information about existing
> payments, clients could make choices about whether to warn users that
> payments may have already been applied for the same account on the same
> payment date, with the same receipt number, e.g.
> This would be a big help at a certain MFI which is currently using the bank
> import plugin extensively, and often finding that users are mistakenly
> uploading the same spreadsheet of payment data multiple times, leading to
> lots of bad data which is not always detected immediately and significantly
> time-consuming to correct when it is detected.
> The new interface method prototype could look like the following, and its
> implementation could look like that in the attached file. Before I go
> further with extending the plugin with logic to detect duplicate records,
> does this seem reasonable? Would it be OK to add this to the AccountService?
> /**
> * Lookup all payments associated with a given account.
> *
> * <at> param accountRef is a reference to the account for which payment
> information is requested.
> */
> public List<AccountPaymentParametersDto>
> lookupPayments(AccountReferenceDto accountRef) throws Exception;
> thanks,
> Sam
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
