|
||||||||
|
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
Keith,
For capturing family member details, would the option be available in the 'Vanilla' version of Reference UI (specifically, the relevant table is already a part of the initial database dump while using the 'datatable' approach)
The reason I ask this if that though adding additional fields through the 'datatable' approach would be very easy for a specialist,it will never be simple enough (even if we have a very simple UI for the same) for a regular end user who would want to start using the system as is without spending time on configuration etc and capturing family member details seems a generic enough requirement
>>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
The latter approach sounds good to me as it would be more generic(If GK specifically wants the former approach, we can probably make the modification after we fork the UI specifically for GK)
I'll check with GK about the queries regarding Guarantor (Might take a couple of days as there is a holiday in India. Will move it to a separate Jira issue for now)