|
||||||||
|
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
Vishwas, and you would be right that we dont want to go adding 'constraints' all over the place but in the scenario mentioned I think its fair to assume that if you are forming a group thats under control/admin of a given branch that its 'activation' date wouldnt be before the date the office 'opened' - then again - maybe i should never of put office opening date into the office area first thing and you wouldnt have a need for these date contrainsts.
But its there now, we have similiar contraints for clients so should be the same for groups/centers.
When it comes to splitting a branch or merging branches or tranfering group to another branch (you dont have to do these contraint checks - its different api/functionality for backend.