|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows:
Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ Mifos-issues mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-issues
On top of the closing client functionality most MFI's would capture the closure reason (as in mifos).
First off, add a foreign key column say "closure_reason_cv_id" to m_client (pointing to code value). Create a new system code, say
"ClientClosureReason". Also another column "closedon_date" would also be needed to track the closures
The api for closing the client would likely be in the format /api/v1/clients/
{clientId}?command=close.
request body
{
"locale": "en",
"dateFormat": "dd MMMM yyyy",
"closureDate": "01 March 2011"
}
Client closure should throw an error is any non-closed loans or savings are present for the client. Client closure dats should also be greater than or equal to the closedon_date of his loan and savings accounts