Binny, That does sound like a good cleaner suggestion and easier to handle for 3rd parties when they might be building in new products - having a completely separate screen for them would be nice.
So the user would first click Admin >> Savings Products >> and then a new page would load and there would be a list of links or icons/links on it for the various advanced savings products or would the Savings Products be a collapsible menu (not an entirely new page?) This is sort of a separate topic but related to the screenshot you shared - what is your thought on wizard-style product creation interface versus single page. Single page might be quicker for power users but wizard might be cleaner and more intuitive for less savvy users. Ed On Wed, Mar 5, 2014 at 10:51 PM, Binny Gopinath Sreevas < [email protected]> wrote: > Ed, > > > > My thought was that we should have each of the product types as separate > links in the products screen (Grouped as below). Gives a better navigation > for users - is my opinion. > > > > Deposit Products > > o Savings Account (Overdraft related fields will be hidden) > > o Current Account (Overdraft limit will be displayed additionally and > won't have minimum balance field) > > o Term/Fixed Deposits (Nominal Interest rate and Minimum opening > balance will be removed from screen, other fields like interest rate chart, > etc. will be enabled along with premature closure conditions and minimum > and max term etc.) > > o Recurring Deposits (similar to Term deposits, but with additional > details like minimum and maximum number of deposits and period of deposits) > > > > Loan Products > > o Loans > > o Tranche/Multi-Disbursement Loans (with additional tranche related > features enabled - like number of tranches and fixed instalment amount etc.) > > > > Here is a screen shot of the Term deposit product definition screen that > Ashok and I have been trying to optimize. > > > > Please let me know if you have any comments. > > > > > > Thanks and Regards > Binny Gopinath Sreevas > > Skype: binny.gopinath > > > > > > *From:* Ed Cable [mailto:[email protected]] > *Sent:* 06 March 2014 00:05 > *To:* mifos-users > *Cc:* deanna; Binny Gopinath > *Subject:* Product definition user experience for advanced savings and > loan products > > > > Binny, > > > > What is the proposed design and user workflow for the definition of more > advanced savings and loan products? > > > > Since we now have tranche (housing loans) as a more advanced loan product > and soon to have fixed and recurring deposits as well as current accounts > as more advanced savings products, I think we need to clean up how these > are defined. > > > > I would propose these be specific loan or savings product types which you > select upon initial product configuration and then the fields available to > configure change based on that selection. Do we have any such plans? > > > > I would propose we improve the product definition user experience so: > > > > 1) We keep the overall UI for defining products relatively clean and not > cluttered by settings that aren't relevant for every product > > 2) A user more explicitly knows that they can create a variant of a > savings or loan product - right now the ability to create a tranche loan or > current accounts is quite hidden in the parameters of a loan > > > > The ideal approach would follow closely what you had mocked up in the > attachment. > > > > A user would go through relatively the same workflow for creating a new > product (i.e. admin >> select savings or loan products >> create a new > product) *but would first select the type of product from a drop down*(i.e. > passbook/basic savings, fixed deposit, current account) and then the > product parameters and fields only relevant to that type of product would > be displayed. > > > > This would seem to also work well once we re-implement the wizard-type > view for product creation. > > > > Alternative approaches would be: > > > > 1) As we have it, as mere tickbox settings in one general product > configuration but have these more explicitly called out (i.e. a section for > current account settings) but this wouldn't help in hiding those settings > that don't apply > > 2) Have current account definition be entirely separate section from > savings product definition (i.e. another level of navigation at the same > level as savings products or beneath savings products) but I think this > would grow too cluttered as we add more and more products. > > > > Deanna - any thoughts? > > -- > > *Ed Cable* > > Mifos Community Manager > > Director of Community Programs, Mifos Initiative > > [email protected] | Skype: edcable | Mobile: 484.477.8649 > > > > *Collectively Creating a World of 3 Billion Maries | > *http://openmf.org<http://mifos.org> > <http://facebook.com/mifos> <http://www.twitter.com/mifos> > > > > *Note:* As of Jan 1, 2014 my email has changed from > edcable@*openmf*.org<[email protected]> > to edcable@*mifos*.org <[email protected]>. Please update your address > book accordingly. > > > > > -- *Ed Cable* Mifos Community Manager Director of Community Programs, Mifos Initiative [email protected] | Skype: edcable | Mobile: 484.477.8649 *Collectively Creating a World of 3 Billion Maries | *http://openmf.org<http://mifos.org> <http://facebook.com/mifos> <http://www.twitter.com/mifos> *Note:* As of Jan 1, 2014 my email has changed from edcable@*openmf*.org<[email protected]> to edcable@*mifos*.org <[email protected]>. Please update your address book accordingly.
<<inline: image001.jpg>>
------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________ Mifos-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-users
