ISO 8601 Calendar Week Configuration

[FlorianA]

Hi ServiceNow Community, We've just implemented ISO 8601 calendar week configuration on our DEV instance and ran comprehensive testing. Before rolling out to TEST and PROD, I'd like to validate with the community if we've covered everything or if there are additional areas we should test.

WHAT WE IMPLEMENTED:System Properties Changed:

glide.ui.date_format.first_day_of_week = 2 (Monday)

glide.db.week_numbering = iso_week (ISO 8601 standard)

glide.sys.default.tz = Europe/Berlin

1. System Analysis

• Checked all active reports for week-related configurations

• Found 7 reports named “weekly” or “per week”

• None use actual week grouping (group_by = week)

• All rely on date intervals rather than week numbers

2. Automated Testing

• Verified ISO 8601 week logic:

  • KW 1 2025 starts on Mon 30 Dec 2024 ✓

  • First Thursday (2 Jan 2025) is in KW 1 ✓

  • Current week (7 Nov 2025) = KW 45 ✓

3. Component Search

• Business Rules with week logic → 0

• Script Includes with week logic → 0

• Client Scripts with week logic → 0

• Scheduled Jobs using weekly logic → 0

4. Manual Verification

• Reports display Monday as first weekday

• No KW aggregation in existing visualizations

QUESTIONS FOR THE COMMUNITY

1. Any hidden areas affected by week configuration?
   (Data Collectors, SLA calculations, Business Calendar, Notifications, Workflows?)

2. Should we test Performance Analytics?
   (Currently disabled. Anything to consider if we enable it later?)

3. Any out-of-box features that rely on weeks?
   (Task escalation, workload mgmt., resource calendars, ITSM?)

4. What about integrations?
   (REST API calls, imports/exports, mail templates with week variables?)

5. Year-end transition: any gotchas?
   (We validated KW 1 2025 = Dec 30 2024. Any issues around year change?)

6. Timezone impact?
   (We use Europe/Berlin. Anything special for multi-timezone setups?)