Hi!
> Given that GK is the only MFI (right now) who needs to fill out these > fields-- we need to make sure that turning on/off these additional > fields is configurable. We don't want to clutter up the create-client > pipeline with several new fields that aren't commonly used. I am pretty convinced this is the way to go. Seems very sensible. I will make the appearance of this field configurable. "Will you be adding those 3 lookup fields to the Lookup Options in Mifos then? What kind of validations are you planning to do on all the additional fields?" I will be using the current lookup_value tables in Mifos. "Did you decide not to make the # fields GK needs dynamic then?" For now no.Though I haven't really given this much thought. :( If I do make it dynamic, I don't see how it will be any better than the create custom field option already present. (i.e i can't write validations for the dynamic fields) "Will be great if you can share some mockups/screenshots as you work on this." I do have a screenshot that i had sent to Dheerendra the day before. It just had a preview pic of what the final page was intended to look like. Please ignore the fields. This was just to clarify with them on whether this was the kind of functionality they were looking for. GK seemed satisfied with this. http://tinyurl.com/ylkllaz Ryan, regarding the usage of Custom fields. GK did give it a try and they decided it didn't really suite the functionality/ease of use that they were seeking. Also Lack of validations is a big pain and the current system takes only string input. -----Original Message----- From: Kay Chau [mailto:[email protected]] Sent: Thu 10/8/2009 6:31 PM To: Mifos functional discussions Cc: [email protected]; Thandavarayan, Parthasarathy Subject: Re: [Mifos-functional] [Mifos-developer] Feature:Capturingadditional details oftheclients family Chandan, Can you do the same as you did for the age enforcement feature and add a page to the mifos wiki to detail this feature? > Given that GK is the only MFI (right now) who needs to fill out these > fields-- we need to make sure that turning on/off these additional > fields is configurable. We don't want to clutter up the create-client > pipeline with several new fields that aren't commonly used. Agree with Emily that these should be configurable. > Relationship id, customer id (from customer table), first name, last name, Date of birth, relationship (lookup), living status (lookup), gender(lookup) Will you be adding those 3 lookup fields to the Lookup Options in Mifos then? What kind of validations are you planning to do on all the additional fields? > GK also wanted to know If the number of fields could be made dynamic. As in the ability to make it greater than 5 tomorrow. We were of the opinion that since this will involve schema and code changes it will be really hard to make the fields dynamic. Did you decide not to make the # fields GK needs dynamic then? Will be great if you can share some mockups/screenshots as you work on this. Thanks for following up on this list! Kay > -----Original Message----- > From: Emily Tucker [mailto:[email protected]] > Sent: Thursday, October 08, 2009 2:48 PM > To: [email protected] > Cc: [email protected]; [email protected] > Subject: Re: [Mifos-functional] [Mifos-developer] Feature: Capturingadditional > details oftheclients family > > Responding only to mifos-functional list-since my response relates only > to the functionality aspects of the email below... > > >I have been working on this feature for a couple of days now, > >I thought I will update the group on my status and issues. > > Thanks for the update, Chandan-- and sharing your ideas on your > approach. > > >Please suggest improvements to this control flow/ structure... > >{I initially thought that the client family details could > >be put on the same page as the first page (had modified the jsp to > >reflect this thought process), but there was a opinion that the > >family details could be moved to a new page. I feel that this is a much > better idea.} > > Given that GK is the only MFI (right now) who needs to fill out these > fields-- we need to make sure that turning on/off these additional > fields is configurable. We don't want to clutter up the create-client > pipeline with several new fields that aren't commonly used. > > Given that, I don't think having a separate page makes sense. Because > most MFIs would disable/hide these fields, the page would be blank. (The > alternative, of course, is that you build it so the page only displays > if those fields are enabled-- but that approach seems too complicated > for simply adding additional fields). > > Emily. > > > ------------------------------------------------------------------------ ------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Mifos-functional mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mifos-functional ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Mifos-functional mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-functional ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Mifos-functional mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-functional
