Aman-Mittal opened a new issue, #766: URL: https://github.com/apache/fineract-backoffice-ui/issues/766
### Summary On **Client → New Account → Fixed Deposit** (`/products/fixed-deposits/create?clientId=…`): 1. Choosing a product doesn't pre-fill its amount, term or rate. All stay empty, including the required **Interest Rate %**. 2. **Frequency** shows a preselected value (component value `2` = Months), but the form control is invalid until the user opens the select and picks Months again. In both cases Save is disabled and **nothing on screen says why**. ### Environment - App: https://aman-mittal.github.io/fineract-backoffice-ui (deployed `main`) - Backend: `sandbox.mifos.community`, tenant `default` - Role: superuser - 2026-10-16 ### Preconditions FD product `E2E-AUDIT-20261016 FD` (default deposit amount 1000, chart 5%) and an active client. ### Steps to reproduce 1. Client → **New Account → Fixed Deposit**. 2. Choose the product. Observe Amount, Period and Interest Rate stay empty. 3. Enter Amount `5000` and Period `12`. Save is still disabled. 4. Enter Interest Rate `5`. Save is **still** disabled. The only `.ng-invalid` control is `ion-select[name=depositPeriodFrequencyId]`, which already shows a value. 5. Open Frequency and pick **Months**. Save becomes enabled. ### Expected behavior Product selection pre-fills the deposit amount, term and rate from the product or template (`GET /fixeddepositaccounts/template?clientId&productId`). The default Frequency is valid. A disabled Save explains which fields are missing. ### Actual behavior As above. After step 5 the account saves correctly: ``` POST /fixeddepositaccounts → 200 { depositAmount 5000, depositPeriod 12, depositPeriodFrequencyId 2, nominalAnnualInterestRate 5, submittedOnDate "16 October 2026" } GET /fixeddepositaccounts/1 → maturityAmount 5255.84, maturityDate 2027-10-16 ``` ### Impact An officer opening a term deposit has to know the product's terms by heart and discover through trial and error which field blocks Save. The rate in particular should come from the product's chart, not be retyped (risk of mismatches, similar to #761 for savings). ### Suggested investigation Load the account template on product change and patch the form. Initialise the frequency control with a value in a way that marks it valid (or default it in the form model rather than only in the view). Add the shared "complete the required fields" hint the client wizard already uses. ### Verification status Reproduced. ### Related endpoints `GET /fixeddepositaccounts/template`, `POST /fixeddepositaccounts` ### Acceptance criteria - Choosing a product pre-fills amount, term and rate. - An untouched default Frequency is valid. - A disabled Save names the missing fields. ### Related issues #761 (savings rate not taken from the product), #295. -- 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]
