[
http://mifosforge.jira.com/browse/MIFOS-5160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=70787#comment-70787
]
Ryan Whitney commented on MIFOS-5160:
-------------------------------------
Shiva,
I think what you're asking for is something different than the current need
that the collection sheet is meeting. It's meant to match to the printed
collection sheet and be a quick way to get the collections into the system.
Dramatically altering it to meet your needs would break that functionality for
others who aren't as interested in all of that information you are providing
when they are entering collections.
It feels like you want a more master sized view into the MFI and the ability to
make the collections/changes. Seems possible, but I would change that this
become a different type of entry tool that works with the API as opposed to
changing the current collection sheet.
I have heard in the past that more teller like model's of MFI's find clicking
on all the links kind of frustrating, especially for individual payments, so
they might be interested in something like this. STill, seems wasteful in a
lot of ways to have to bring up a whole group/center for entering transactions
for a single client. Maybe the solution for that is to figure out ways to
streamline the individual management. IE, instead of having to go to the
client and each individual loan and savings account, you can just bring up a
view that lets you make transactions for ALL of the client's accounts. This
might be a good solution for users that are also dealing with performances
issues in regards to their network.
But at this point, this is a bit of conjecture. Might help if there was a
deeper dive into the issue, maybe sharing some clear business process maps,
plus some descriptions of what steps the users are currently doing to enter in
the transactions and the time it takes.
For example: Taking a loan payment
1. User searches for client
2. User clicks on client
3. User clicks on loan
4. User clicks on Make Payment
...etc
Time: 45 seconds
> Collection screen user interface
> ---------------------------------
>
> Key: MIFOS-5160
> URL: http://mifosforge.jira.com/browse/MIFOS-5160
> Project: mifos
> Issue Type: Improvement
> Components: Collection Sheet Entry
> Affects Versions: Release 2.2.1
> Reporter: hugotechnologies
> Assignee: hugotechnologies
> Priority: Major
> Attachments: Collection Screen.docx
>
>
> Collection Screen
> It is important that the collection screen is more user friendly as 80% of
> the most user screen is collection and this screen should accommodate both
> Savings, Loans and other collections.
> Since, the mifos product is used by rural industry it becomes more important
> to give user friendly interface.
> We are planning to develop a screen considering the below details.
> 1. Collections can be performed at POS (Branch / HO). Member comes to
> Branch or HO and pays the installment amount at cash counter, as per the
> government regulations, evidence towards the payment to be given to member as
> a receipt printing
> 2. or Loan officer goes to individual member or group and enters the
> collection amount against each member. Here, there should be a feasibility of
> displaying the list of members mapped with that group.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://mifosforge.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
RSA® Conference 2012
Save $700 by Nov 18
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
