Alta bloqueada: la fecha de expediente se rechaza siempre (anterior, actual y futura)
Reported by Fabri in the online tracker (Para Elazar, unticketed row, download pending): 'No nos permite registrar fecha de expediente, ni anterior, ni actual, ni futuro por lo que no podemos registrar un alta. La restriccion tiene que ser de una fecha futura a la actual.' Donde mirar: 'En vehiculos al generar un alta, y crear colectivo no acepta la fecha, probamos anterior, actual y posterior, dando error en todos lo casos'. Alta is blocked end to end in dev01: every date value is refused, so no vehicle can be created. Fabri states the intended rule explicitly - the only date that must be refused is one LATER than today; past and current dates are legitimate. Candidate cause to measure first, not assume: MOVILBA-547 (maximum expediente date) closed 2026-10-05 16:49 ART and shipped a ceiling the same day this was reported, so a regression in that comparison is the first thing to check - an off-by-direction or a null/parse failure in the ceiling rejects every value, which is the observed shape. Second candidate, independent: MOVILBA-288/349/637 made numero and fecha de expediente mandatory on every tramite in v5.6.166, so a required-field error could be surfacing as a date error. Reproduce on dev01 first, then confirm whether PROD carries the same build. Elazar also raised the lezama 2026-10-05 ~23:xx crash plus wrong host clock as a possible cause: that host runs agents only, not the app, so it cannot set the app server clock - rule it in or out by measurement rather than citing it.
Activity
-
Started source tracing after checking deployed date validator; still must reproduce the reported create flow on DEV01 as required by the item before proposing a code fix.
-
Source check: createColectivo requires expediente and fechaExpediente, then validarFechaExpediente accepts valid YYYY-MM-DD through America/Argentina/Buenos_Aires today and rejects only later dates; form posts input type=date as YYYY-MM-DD. No source-level date defect identified. Required DEV01 repro attempted with DEV01_AGENTWRITE: first session reached alta form and fetched authenticated dropdowns; a subsequent login remained at /user/login before any form submission. No Alta was created. Need a stable authenticated DEV01 session/account check to complete the required runtime control.
-
Current DEV01 v5.6.172 disproves the blanket rejection. Authenticated write test with all required controls valid: date 2026-10-06 (today, ART) passed server and navigation reached /vehiculos/QZ657QX. Rendered detail shows Fecha de Alta and Vigencia desde 06/10/2026, and history row fecha de alta 06/10/2026 with the submitted expediente. Evidence: /data-lezama/movilba/evidencia/MOVILBA-712/2026-10-06-date-probe.json (SHA256 to append from command output). One DEV test vehicle was created; no existing row changed. No code defect reproduced on current build.
-
Evidence JSON SHA256: e07ed919bc2b39390d2aec38651ddc5ee3db0f8ad1650ae2d6fab8b768413f66. The test did not exercise past/future dates; today's successful create is sufficient to disprove the report that every valid date is rejected on 5.6.172.
-
Tracker: moved Pendientes->Resueltos (No reproducido, dev01 v5.6.172) in canon 2026-10-08-1046.