|
||||||||
|
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 |
||||||||
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Mifos-issues mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-issues
So the solution is to separate two different meeting schedule update types:
1) for customers being at the top of hierarchy (mainly centers), anywhere where we can edit meeting schedule from customer's detail page -> this should be update like functional specification says
http://mifos.org/functional-specifications/mfi-information-setup/meetings
2) for customers who are switching their membership (eg client switching group), their meeting schedule should be updated from the day that group change is made
Note that those customers cannot have any active loan accounts or any active periodic fees so we treat them like new customers
Their disbursement date will be correct then