Hi!
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. Please suggest
improvements to this control flow/ structure.
Envisaged control flow ;
[Page where the client details are entered] -> [Page where family
details are entered]->[Page where the MFI info is entered]
{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.}
Database modifications:
Currently the spouse/father names go to the customer_name_detail where
there are 2 entries/customer. With the additional family info, we could
continue to use this table for the names,
But since only the first name/last name for the additional family member
would be required I propose we create a table client_family_details with
these fields.
Relationship id, customer id (from customer table), first name, last
name, Date of birth, relationship (lookup), living status (lookup),
gender(lookup)
Development:
Since it seems to be a new page, I will be creating an action/actionform
classes. Also an entity bean to hold this family data. I am looking at
the writing into the persistence part now though. There are many
classes/tables that have the following string patterns spouse*father* .
I am not sure whether I should revamp this naming schema.
Regards
Chandan
From: [email protected] [mailto:[email protected]]
Sent: Monday, September 14, 2009 2:35 PM
To: [email protected]
Subject: Re: [Mifos-functional] Feature: Capturing additional details of
theclients family
Hi Ryan
That's a great idea. But, how do I link the accounts?
Currently the functionality is not for tracking guarantors. There is a
possibility that there may be a need for more information. But it was my
opinion that adding additional fields dynamically with all the
properties of the already existing fields will be a problem as it will
require schema/code changes ? But that was for the structure that I had
in my mind. I am not really sure whether it will apply to the final
design that we implement. Maybe it will possible to add fields here with
good validation?
Regards
chandan
From: Ryan Whitney [mailto:[email protected]]
Sent: Monday, September 14, 2009 1:10 PM
To: Mifos functional discussions
Subject: Re: [Mifos-functional] Feature: Capturing additional details of
the clients family
I'm only replying on the mifos functional list so we can try and keep
the functional and development conversations on the separate lists.
Chandan,
Is this functionality used to track guarantor's? Is there possibility
in the future to need more information?
I'm wondering if it might not be appropriate to change Mifos so they
enter in the family information as an individual account, then you can
link the accounts from the active client to their family member. This
family member account would either be marked as inactive (ie, we have
information on the client but they are not active) or create a new
status for these type of accounts (something like "not a client").
This might be a lot more work but would be a good step forward to make
Mifos more flexible (I'm thinking about how someone might use this for
Guarantor information, and that guarantor's might be clients within the
MFI or not)
Ryan
On 9/11/09 14:40, "[email protected]" <[email protected]>
wrote:
Hi
This mail is to brief everyone about the additional requirements that GK
currently has in the client info page
To start with GK is not satisfied with just the spouse/father's name
being taken as an input. They will need these other data to be captured
as they are rolling out a Micro Insurance product soon.
They currently have 5 fields in mind
1) First Name, Second Name, Last Name
2) Date Of Birth
3) Relation to the client*
4) Gender
5) Living status**
*Relation to the client will be configurable by the user.
**This will specify whether the person is living with the client or not.
On the UI front we thought we could make it a dynamically generated
table depending on the number of entries to be made. We are not sure how
heavy this will make the application. But for now this is what we have
in mind.
Schema wise it will mean creating a new table that can store this
entries with references to the customer ID. Currently all names are
being stored in the customer_name_detail table. After these changes
maybe there won't be any need for this table.
Regarding on the way to fill data for the old customers, Gk told us that
they would, after this patch is submitted, be editing the client details
in the edit client info page. That seems a very reasonable solution.
Date of birth will have just simple validations for whether the date is
correct. We are exploring the option of providing a calendar option for
the date entry.
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.
This is about it for now.
Thank you and regards
Chandan
Chandan Rao H * Associate Software Engineer * SunGard Technology
Services *Embassy Icon, 6th Floor, Infantry Road, Bangalore 560001 India
* Tel +91-80-2222-0501 Extn:3240 , Mobile +91-9686601284*
http://www.sungard.com/sts
Email: [email protected]
CONFIDENTIALITY: This email (including any attachments) may contain
confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited. If you received this email in error,
please notify the sender and delete this email from your system. Thank
you.
________________________________
------------------------------------------------------------------------
------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day
trial. Simplify your report design, integration and deployment - and
focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
________________________________
_______________________________________________
Mifos-functional mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-functional
--
Ryan Whitney
Mifos Technical Program Manager
[email protected]
Mifos - Technology that Empowers Microfinance (www.mifos.org)
<<image001.png>>
------------------------------------------------------------------------------ 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
