|
||||||||
|
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 |
||||||||
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________ Mifos-issues mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-issues
Vishwas,
On this topic. Right now the intention was to make the creation of a client the most basic thing possible capturing only the most basic details (that every mfi would capture).
Once the client was added on the system. The data entry person could proceed to add any extra data required by a given MFI where we are using this 'datatable' approach.
So the question is does the workflow of the ui have to allow 'all' details to be captured (right now) or can we continue to do it as:
1. create client (most basic info)
then in any order
2. add family member details
Moving forward to loans:
The Co-applicant seems specific to GK (might not be widely applicable) whilst
'guarantor' does seem like something normal and general to loans (optional relationship). With gaurantor the question is, sometimes the gaurantor is an existing client, sometimes it might be someone outside of the mfi-client relationship.
In GK-maarg case, its probably always an existing client (we can ask that), for other mfis though might need ability to add specific details of a gaurantor.