Title: Message Title
|
|
>>If you are storing historical reference of office account is associated with - when a transaction is added we can always use a temporal pattern to make sure the transaction goes against the right office based on the date e.g. getOffice(date)
I guess I am making a mountain out of a molehill here....
But we wouldn't want that too, when a client is in a new branch, any action done by the new branch users should not affect the accounting books of the older branch.
I would think a simple quick fix would be to simply disable transactions on any closed loan when it is moved between branches, we can always revisit it if there is a real world scenario where a closed loan is moved between branches and then transactions are performed against it etc...
|
|
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
