Title: Message Title
|
|
|
|
Just FTR for any volunteers possibly wanting to picking this up: In addition to "mobile number fields directly on client and staff tables.", also "don't need to store 'other numbers' just the current number associated with the client/staff (which will and should be allowed to change)" + "store primary number in core and other secondary numbers can always be part of additional data" (as per mailing list thread).
MIFOSX-779 has some ideas for future "robustness" work for these new fields - beyond the basic support which this issue would provide.
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues