|
||||||||
|
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
There was an option of adding an api that allowed individual charges to be added/deleted to a loan product rather than the aggregate manner described above e.g. /loanproducts/
{Id}/charges/{Id}But I didn't think it works as well.
On the validation... One reason not to get too invested in validation is that it might be better to removed the is_active field from the charge table rather than have the validation required to maintain it... ie if no field then no checks on change of status needed and its not that important.