Audit Engagement — end_date / Fieldwork planned end jumps wrong year in Workspace

Mira1992
Mega Sage

‎12-10-2025 01:48 AM

Hi everyone,

Summary (what's broken): On an Engagement record in Audit Workspace — when I set the duration, the planned end date jumps to a wrong year. 
Example:
Fieldwork planned start is set as: 2025-12-10 10:11:25
I set the Days (duration) to 10 days and expect the Fieldwork planned end to be 2025-12-20 10:11:25
But it shows 2031-05-03 17:16:25. Once I refresh the page, date is correct but at first it shows incorrectly.

Details:

  • Table: sn_audit_engagement

  • Client Script (only runs in Workspace): “WS planned end date for duration change” — SYS ID: a994b79c5b0020102d4ee96d7981c780

  • Script calls sn_audit.AuditUtilsWS.calculateEndDate() — Script-Include SYS ID: 3b3232410f322010878cddcd58767e37

Observed behavior:

  • In Workspace: setting duration (e.g. +5 or +10 days) causes end_date to jump to a far future year (e.g. 2031) instead of adding days.

  • After a page refresh, end_date recalculates correctly (start date + duration).

  • In backend / classic UI: everything works correctly — no weird year jump.

  • When I disable the Client Script, Workspace behaves correctly too (calculation works fine).

What I’m asking:

  1. Has anyone seen the same behaviour (Workspace-only, wrong-year on duration change, fixed by refresh)?

  2. Is AuditUtilsWS.calculateEndDate() expected to work correctly in Workspace — or are there known limitations for date calculations in Workspace UI?

  3. Is it common / acceptable to disable such Workspace-only Client Scripts and rely on server-side calculation only?

  4. Could this be a bug in Workspace environment / version of scoped app, or a configuration issue?

Thanks for any feedback or similar experiences.

Best,
Mira

0 Helpfuls