Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

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

Mira1992
Kilo Sage

yesterday

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
  • 95 Views
1 REPLY 1

Connor Levien
ServiceNow Employee
ServiceNow Employee

yesterday

@Mira1992 I would suggest raising a Hi ticket for this to get resolve

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

    • I have heard of this happening but for other workspaces

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

    • It is intended to work for Workspaces I suspect there is a bug with handling timezones or something thats causing it

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

    • If you use a Server side only calculation it wont update in the UI as changes are made which can be confusing for end users.

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

    • Generally I would suggest checking that your workspace plugin version is the same as the underlying app first. If they are different there can be issues. Configuration and other things could be impacting it. I would suggest to raise a Hi ticket so a support engineer can find out exactly whats happening in your environment

 

0 Helpfuls