Hi Arpita, Some more comments are inline below. Let me know your thoughts :)
> 1. Purpose of Loan - Thanks for the link. It says that some of the fields > can be made optional/mandatory only during installation, and "Purpose of > Loan" is one of them. Therefore, the option to make it mandatory/hidden is > not there in UI and it suits the given specs. > Thus, its not a bug. Oh, excellent comment. I might be mistaken, but all of the other fields that are listed on the list on the configuration options page as being able to be made optional/mandatory are all configurable in the UI in the "Define mandatory/hidden fields" feature. I know the note on the FS says that they are only to be specified at installation time, but that goes for all of the fields in the list, not just the "Loan Purpose" field - so this is an inconsistency that it is not included in the list in the UI. So, I still think it's a bug. Am I still mistaken or do you agree? If you agree, can you open the item in the issue tracker? > My questions: i) Should the loan officer be allowed to make a past dated > "payment entry"? (That is, say if on Friday the loan officer wants to make > an entry for payment made on Wednesday, should he be allowed?) At present > the system allows this and I think it should allow so that a Loan officer > can rectify any mistake/ommission. Moreover, the feature "Redo Loans" is > available only to rectify wrong disbursals not repayments. Ah, yes. Now I see what you mean. Mifos has a feature that allows the user to configure whether back-dated payments are allowed. So, if this configuration is turned on, the user can enter transactions dated earlier than current date (but later last meeting date). See 'back dated transactions' on this page for more detail - http://mifos.org/knowledge/functional-specs/configuration-options#3_4_Mi scellaneous One thing we will have to investigate is how Mifos handles this with the new feature that allows payments on non-meeting days. Does the system allow the user to enter transactions dated earlier than the current date but no earlier than the last meeting date, or does the system allow the user to enter transactions dated earlier than the current date but no earlier than the last repayment date. We didn't specify this explicitly in the design of the "Loan schedule independent of meeting schedule" feature so we should understand how it works and if it needs to be modified. > ii) The system doesn't allow to enter a date of repayment in the past > which > precedes the last meeting date. (That is, say a payment was made on the > first thursday of a month instead of monday. The officer forgets to make > the entry. On the third week, he realises his mistake and wants to make an > entry for the said payment. But the system will throw up a message "entry > prior to the last meeting date not allowed". Thus, the Loan officer can > make a past dated entry but only till the last meeting date (in this case > only till second Monday of the month). So, I wanted to know whether this > kind of function is intended or is it a bug?? This is intended for now. I think it was an explicit decision to only allow back dated payments up until the prior meeting and not allow back-dated transactions prior to that. We can talk through some of the reasons around that on skype/IRC if you are interested in hearing more details about that. So, it's not a bug but an area we could potentially consider enhancing in the future if the need arises. Thanks, Aliya ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mifos-functional mailing list Mifos-functional@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mifos-functional
