Hi Arpita, > This is in relation to the functional irregularities/issues noticed in the > test server:
Thanks for your feedback. I'm going to jump in on these even though I haven't been part of recent discussions with the team - so please excuse me if I've made any incorrect assumptions. Also, I've copied the functional list so that everyone knows of your findings. > 1. Loan Account Search By ID - Checked all kinds of loan. Found that the > search option was working fine for loans in varying statuses namely, > Active > (Good/Bad), Approved, Cancel, Closed (Withdrawn/Written Off/Obligation > Met), Reversed Loan. [Issue 1534: Resolved] Great! One down. It's nice to see bugs miraculously fix themselves ;) > 2. Purpose of Loan - In 1.1, in the Loan Account Information page, the > "Purpose of Loan" field appears without an asterix and thus is not > mandatory. Therefore, I added one more field as "Purpose of Loan" and made > it mandatory. However, I realised later that from front end only > additional > mandatory/optional fields could be added. These fields appear under the > head "Additional Information" in the Loan Account Information page. To my > dismay I realised that there is no option to make the existing "Purpose of > Loan" field mandatory or remove it from the front-end. Ah, interesting. According to our functional specification, the user should be able to modify whether the "Purpose of Loan" field is hidden or mandatory: http://mifos.org/knowledge/functional-specs/configuration-options#3_10_H idden_Mandatory_data_field It sounds like you've found a bug. Can you enter this into the issue tracker and assign to mifostriage? Emily or others can comment whether I'm mistaken about the functionality, but I'm pretty sure the ability to make this field mandatory or optional should be in the UI in v1.1. > 3. Ability to Repay Loans on non-meeting days - This additional feature > enables a user to repay an installment on non-meeting days. In doing so, > the system allows an user to give a date in the past. However, the system > does not allow a past date prior to the last meeting date. This can act as > a barrier in a scenario where the user needs to give effect to a repayment > from a past date which precedes the last meeting date. When you say that the system allows the user to give a date in the past, which date are you referring to? The disbursal date for the loan? I'm a bit confused. For the feature that allows the user to make disbursals and repayments on non-meeting days (http://mifos.org/developers/wiki/LoanIndependentOfMeeting), the system should constrain the user to enter a disbursal date greater than or equal to the current date but not allow disbursal dates in the past. Also, for this feature, the user does not specify any of the repayment dates - the system automatically determines the repayment schedule based on the disbursal date, repayment days (e.g. "First Thursday of the month), etc. This feature should never allow the user to enter repayments in the past. The only feature that should allow the user to enter dates in the past is the "Redo loan disbursal" feature (http://mifos.org/developers/wiki/RedoingLoanDisbursals). It sounds like you agree with this from the comment below. But, I'm not sure how the feature you describe in #3 is different from the feature you describe in #4. Can you clarify? > 4. Ability to Disburse Loans on non-meeting days - This feature allows the > user to disburse a loan on non-meeting days. The allowable days are the > current date and any past date not prior to the last meeting date. > However, > a feature called "Redo Loan" already exists wherein the user can rectify a > mistake and redo a loan to the right customer with effect to a past date. > In such a case, "Disbursement of loan on non-meeting days" feature should > only accept current date. Because the need to disburse a loan with effect > from a past date will arise only in case of a mistake. And to take care of > such mistakes, "Redo Loan" feature is already there. Yes, I agree. For the feature "Loan schedule independent of meeting schedule" (http://mifos.org/developers/wiki/LoanIndependentOfMeeting) which adds the ability to schedule disbursals (and repayments) on non meeting days, the user should not be allowed to enter disbursal dates in the past. They should only be allowed to enter the current date or dates in the future. You are also correct that the only feature to enter disbursal or repayment dates in the past is the "Redo loan disbursal" feature. If the system is allowing disbursals in the past for the regular loan account creation path, you should open an item in the issue tracker for this. > 5. Redo Loan - This feature allows an user to rectify his mistake of > disbursing loan to a wrong customer by disbursing a loan to the right > customer with effect from a past date. However, at present the system > allows to "Redo a Loan" on a past as well as future date. Future dated > disbursals in this feature seems redundant. Yes, totally agreed. Thanks for entering this one in the issue tracker (https://mifos.dev.java.net/issues/show_bug.cgi?id=1549 for everyone's reference). > Since I have already spoken to you all about these issues, thus am mailing > it only to you instead of the functional listserv. I thought it would still be good for the mailing list to see the comments, so I hope you don't mind that I included everyone again. Thanks, Aliya ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Mifos-functional mailing list Mifos-functional@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mifos-functional
