Aman-Mittal opened a new issue, #671: URL: https://github.com/apache/fineract-backoffice-ui/issues/671
Three unrelated findings from a browsing pass over a running instance. Each is small and independent; grouped so they are not three near-empty issues. --- ## 1. A mandatory field is not marked mandatory on the transaction forms On the savings deposit form, `paymentTypeId` is mandatory server-side, but the field carries no required marker and **Save is enabled without it**. Submitting gets: ``` Validation errors exist. • [paymentTypeId] The parameter `paymentTypeId` is mandatory. ``` That is raw platform phrasing — bracketed parameter name, backticks and all — shown to a branch operator who filled in a form and pressed Save. The platform rule is knowable before submit, so this is a client-side validation gap, not an error-reporting one. Worth checking the other transaction forms for the same thing rather than fixing only this one. ## 2. `BUSINESS DATE: -` is permanent when the instance has no business date `GET /businessdate` answers `[]` when the feature is not configured. The header chip then renders a literal `-` for the entire session, next to the global search, and never says anything. Suggest hiding the chip when there is no business date, rather than reserving header space for a dash. ## 3. The sign-in failure message cannot distinguish a wrong password from a wrong server `config.json` ships `fineractApiUrl: "/api/v1"`. `proxy.conf.json` maps `/fineract-provider` only. So signing in with the sign-in page's **default** endpoint selection in the documented local setup produces: ``` POST /api/v1/authentication → 404 ``` and the page reports: > Login failed. Check credentials/server. A 404 on the auth endpoint is a configuration problem. A 401 is a credentials problem. A network error or a CORS rejection is a third thing. One sentence covering all of them leaves the operator guessing, and it is the first screen anyone meets. Two parts, which could be split: - **The message.** Distinguish 401 from 404/0/CORS, so the text points at the thing that is actually wrong. - **The default.** `SETUP.md` tells a local developer to pick **Local Proxy Server** explicitly, because the shipped default is the same-origin path used by the Docker deployment. That is a defensible default for production, but it means the out-of-the-box selection fails for anyone following the local setup — worth deciding whether the dev-time default should differ. --- All three observed on `origin/main` against `apache/fineract:latest` on 2026-10-02. -- 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]
