...
- User clicks on "Define Loan Product"
- On Loan Product Definition page, there are options to specify loan amount or # of Installments by loan cycle # or previous fully repaid loan amount of client. Option should be mutually exclusive.
- By loan cycle number: For this option, user can specify the following for the current loan cycle number of the account owner: _ Loan max amount - for each loan cycle _ Loan min amount - for each loan cycle * Default amount - for each loan cycle
- By last loan amount: For this option, user can specify the min, max and default values for the range of last loan amount paid by the account owner. User will have to specify the following: _ Last loan amount Range - a max of 6 ranges can be specified by the user. The first range will start with 0. When the user fills first end range, say 3000, then second row start range will be filled up with 3001 and so on. _ Loan max amount - for each range _ Loan min amount - for each range _ Default amount - for each range * Validation: ranges should not overlap.
- Loan cycle numbers for which the user can specify the amounts or # of installments are- 0, 1, 2, 3, 4 and greater than 4.
- Loan amount or # of installments field consider successfully repaid loans, not rescheduled loans. Applies just to loans quick cash loans in same product instance.
Note that previous loan can still have late payments and be considered successfully repaid.
Other information
- The min, max and default values can be modified from edit loan product. If this is done, it should be reflected in all the new loan accounts created after the change has been made. It will not affect the loan accounts already present.
- The changes should be applied immediately. This is NOT a batch job.
- The loan cycle to be considered is the product loan cycle.
- When a new loan account is created for a customer, the system should display the min, max and default loan amounts as per the specifications above. All the validations will be as per these values.
...
An implementation was sent in in April of 2007. Jim Kingdon, between then and July 2007, looked at it and decided not to check it in because it has no tests. More minor problems are (1) copy-pasted code to deal with the 5 different rules, rather than an array or some such mechanism, (2) debugging print statements still in place, (3) a few little lines in the diff which don't seem to belong (probably due to not diffing against the exactly correct subversion revision).