Aman-Mittal opened a new issue, #758:
URL: https://github.com/apache/fineract-backoffice-ui/issues/758

   ### Summary
   **Create Client** (Submitted On, Activation Date) and **Create Loan** 
(Submitted On, Expected Disbursement) default their dates to the **browser's 
local date**. Fineract judges "today" in the **tenant's** time zone (or 
business date, when enabled). When the browser's date is ahead of the tenant's, 
submitting with the defaults is refused. Other forms in the same app already 
use the tenant's date from the template (the loan Repayment form defaulted to 
the tenant date correctly), so this is inconsistent rather than inherent.
   
   ### Environment
   - App: https://aman-mittal.github.io/fineract-backoffice-ui (deployed `main`)
   - Backend: `sandbox.mifos.community`, tenant `default`, business date 
**disabled**
   - Browser time zone: Asia/Kolkata. Browser time 2026-10-16 11:25 IST = 05:55 
UTC, and the server `Date` header agreed (05:55 GMT, 16 Oct)
   - 2026-10-16
   
   ### Preconditions
   A browser whose local date is ahead of the tenant's current date. On this 
sandbox that was the case between 00:00 and at least 11:25 IST.
   
   ### Steps to reproduce
   1. **Clients → Create Client**, fill the required fields, leave both dates 
at their defaults, Save.
   2. **Client → New Account → Loan Account**, choose a product, leave dates at 
their defaults, Save.
   
   ### Expected behavior
   Dates default to the tenant's current date (business date when enabled, 
otherwise the date the platform considers today). The submission succeeds 
without the user editing dates.
   
   ### Actual behavior
   ```
   POST /clients  submittedOnDate "16 October 2026", activationDate "16 October 
2026"
   → 400 error.msg.clients.submittedOnDate.in.the.future
          error.msg.clients.activationDate.in.the.future
   
   POST /loans    submittedOnDate "16 October 2026", expectedDisbursementDate 
"16 October 2026"
   → 403 "The date on which a loan is submitted cannot be in the future."
   ```
   For comparison, the loan **Repayment** form defaulted `transactionDate` to 
`2026-10-15` (the tenant's date from the transaction template) and posted fine 
at the same moment.
   
   The client error reaches the user only as a toast containing the ISO date. 
The loan error also arrives as a 403, which reads like a permission problem.
   
   ### Evidence
   Requests and responses above. After changing the dates to an earlier day in 
the pickers, both forms submitted successfully (client id 2, loan id 2).
   
   ### Impact
   Every client and loan entered during the part of the day when the user is 
ahead of the tenant fails on first submit. For institutions whose staff work in 
a different zone from the tenant setting (or after enabling business date for 
COB), this hits every working day. Users are pushed into editing dates by trial 
and error, which invites backdating mistakes.
   
   ### Suggested investigation
   Seed default dates from the server, not `new Date()`: `GET /businessdate` 
when business date is enabled, otherwise a template that carries the tenant's 
date (as the transaction templates already do). A shared "tenant today" signal 
in a core service would fix every form at once. Grep for `new Date()` defaults 
in feature forms.
   
   ### Verification status
   Reproduced on two forms. Other forms that default to today (savings, 
deposits, groups, centers) weren't individually checked.
   
   ### Related endpoints
   `POST /clients`, `POST /loans`, `GET /businessdate`, `GET 
/configurations/name/enable-business-date`
   
   ### Acceptance criteria
   - With the browser ahead of the tenant's date, Create Client and Create Loan 
submit successfully with default dates.
   - With business date enabled and set in the past, defaults equal the 
business date.
   - One shared source of "tenant today" is used by all forms that default a 
date.
   
   ### Related issues
   #748 (date-only fields rendered with time zone), #653 (generated date types).


-- 
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]

Reply via email to