|
||||||||
|
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 Mifos-issues@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mifos-issues
Ok Keith, have assigned the same to Goutham.
My original line of thinking was that we should not be adding such artificial constraints to the API till we have a real need for the same. In most organizations (GK, Chaitanya) it is common enough for groups (and clients) to be moved between branches (branch splits etc). So the original group creation date can be lesser than the current branch it belongs to. So any API driven migration would require a clean up of existing data to ensure these constraints are met.
In my mind, the only real constraint would be that a client /group cannot have a loan created before his creation date