Aman-Mittal opened a new issue, #196:
URL: https://github.com/apache/fineract-backoffice-ui/issues/196
Tracking issue for making the loan product form able to express what the
Fineract loan engines
actually support.
The form could originally create only a basic product. Several settings were
modelled by the API,
returned on every product, and had no control at all — so a product created
in this application
could not use them, and a product configured elsewhere was silently damaged
when edited here,
because the payload is rebuilt field by field and anything unnamed is
dropped on save.
## Sub-issues
- Keep cumulative and progressive loans distinct across the loan screens
- Down payments and multi-tranche disbursement
- Capitalised income and buy-down fees
- Interest recalculation and the remaining product settings
## Outcome
All four are merged. The form now covers down payments, tranches,
capitalised income, buy-down
fees, interest recalculation and its dependent rule chain, charge-off
behaviour, accrual activity
posting, fixed-length terms and the repayment start date rule — each gated
on the engine that
supports it, each carrying plain-language help, and each covered by unit,
mocked and (where the
contract needed proving) backend tests.
## What is still open in this area
- `isArrearsBasedOnOriginalSchedule` and the `*OnDayType` recalculation
fields.
- The capitalised-income accounting mappings
(`capitalizedIncomeClassificationToIncomeAccountMappings`), which belong
with the accounting
section rather than with income recognition.
- `loan-product-form.component.ts` has grown to ~1,750 lines and wants
splitting into per-section
components before it takes on more.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
