From: Keith W. <kei...@gm...> - 2010-10-27 20:14:36
|
Jeff, Kay, Ed, I'll summarise the last few emails. >> +1 for the proposal below I think it will be rare for an MFI to change calculation and posting frequency and we can always add it in later. ok. So for 1.7 (Liela E) release, the following will be the case for savings: Once active or inactive savings account exist against a savings product, the following fields would be 'disabled' (on the UI) and are not allowed to be updated when updating savings product. Interest calculation frequency Interest posting frequency If the savings product is applicable for clients, groups, or centers Type of deposits - mandatory to voluntary, or vice versa Max Withdrawal Amount >> I am concerned about the usability of the edit >> savings product page - how the user will get good indication of this >> situation where accounts are already in the system? Ideally, some >> notification would appear when user first enters the Edit page instead >> of on preview or submit. We would need to disable the form fields on the 'edit savings product' page like what is done with the GL fields. If you want to add a message also saving active/inactive accounts exist for product then thats fine, but i would expect that to be the norm in case of using savings products/accounts. >> Can the following still be changed: >> Balance used for interest calculation This 'Balance used for interest calculation' field refers to the type of algorithm used (average, minimum). Would 'savings users' really want to change a savings products 'interest calculation algorithm' through its lifetime? >> Minimum balance required for interest calculation >> I know that Nuru currently has active savings accounts but they might be considering changing the min balance required for interest. Yes this can be updated along with the interest rate and we will track changes to these fields to make it possible to calculate and post interest correctly. KeithW. On Wed, Oct 27, 2010 at 9:02 PM, Kay Chau <kc...@gr...> wrote: > Oops that is a good point. > > I should refine my proposal to active and inactive savings accounts. > However if ALL accounts of that savings product are in pending approval, > that is okay since those savings accounts haven't started yet. > >> I'm good with proposal if it's effective for both active and inactive >> accounts, and if I better understand how the user will know when >> they've entered this state. I am concerned about the usability of the >> edit savings product page - how the user will get good indication of >> this situation where accounts are already in the system? Ideally, > some >> notification would appear when user first enters the Edit page instead >> of on preview or submit. > > As an improvement, we can add a warning message at the top of the Edit > page that says "There are currently active accounts of this savings > product." > > And then those fields would be disabled... > >> -----Original Message----- >> From: Jeff Brewster >> Sent: Wednesday, October 27, 2010 11:01 AM >> To: Kay Chau >> Cc: 'kga...@gm...'; Udai Gupta (Contractor); 'A good place to >> start for users or folks new to Mifos.'; Keith Woodlock (contact); >> Emily Tucker >> Subject: RE: [Mifos-users] Updating Savings Products >> >> Kay, >> To clarify the proposal you are making, when you say: >> >> >> So we are saying once you create a savings product and there are >> >active >> >> savings accounts under that product, the following cannot be >> changed: ... >> >> If there are inactive accounts for that savings product, we also > should >> not allow the changes. This is important since savings accounts can >> become inactive with the dormancy rule, then reactivate once new >> transactions happen on the account. >> >> I'm good with proposal if it's effective for both active and inactive >> accounts, and if I better understand how the user will know when >> they've entered this state. I am concerned about the usability of the >> edit savings product page - how the user will get good indication of >> this situation where accounts are already in the system? Ideally, > some >> notification would appear when user first enters the Edit page instead >> of on preview or submit. >> >> Jeff > > |