---
sourceDocument: Yokohama ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/platform-administration
Release :
- yokohama
ft:locale :
- en-US
ft:publication_title :
- Yokohama ServiceNow AI Platform Administration
ft:clusterId :
- platadm
bundleId :
- platadm
workflow :
- Platform
---
# Global date and time field format
# Global date and time field format {#ariaid-title1}
* Release version: Yokohama
*
* Updated August 1, 2024
*
*  2 minutes to read
Summarize
 Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
## Summary of Global date and time field format
ServiceNow allows administrators to set default global date and time formats via system properties.
These settings determine how date and time fields are displayed across the platform.
Users can also override these defaults with personal preferences.
Proper configuration ensures consistent and accurate date/time representation in your instance.
Show full answer Show less
## Key Features
* **Date Format Configuration:** The `glide.sys.dateformat` property controls the global date format and is configurable under **System Properties \> System** . The default format is `yyyy-MM-dd`.
* **Time Format Configuration:** The `glide.sys.timeformat` property controls the global time format and is also configurable under **System Properties \> System** . The default format is `HH:mm:ss`.
* **Format Patterns:** Both date and time formats use pattern strings similar to Java's `java.text.SimpleDateFormat` class, with the exception that appending the 'z' character for time zones is not supported in scripts due to validation errors.
* **Date Format Details:** Use four-digit years (`yyyy`) to avoid ambiguous date interpretations. The format supports months (`MM` for two-digit months, `MMM` for names), days (`dd`), and years (`yyyy`, `yy`). Avoid two-digit years to prevent unexpected past/future date calculations.
* **Time Format Details:** Supports both 12-hour and 24-hour formats using `hh`/`h` or `HH`/`H`. Minutes and seconds use `mm`/`m` and `ss`/`s`, respectively. Adding `a` appends AM/PM indicators even for 24-hour formats.
* **Validation:** After modifying date or time formats, validate the changes using the "Validate date and time" script to ensure correctness and prevent errors.
* **User Personalization:** Individual users can personalize date and time formats to suit their preferences, overriding global settings for their sessions.
## Practical Considerations for ServiceNow Customers
* Always use four-digit year formats (`yyyy`) to avoid date misinterpretation issues related to two-digit years.
* Validate format changes immediately to prevent invalid date/time errors in scripts and data entry.
* Be cautious about time zone formatting in scripts as 'z' is unsupported and may cause validation failures.
* Communicate global format changes with your users since personal preferences can override these settings.
* Configure formats centrally to ensure consistency across modules, reports, and integrations relying on date/time fields.
You define default date and time formats globally using system properties.
## Date format
The glide.sys.date_format property defines the date format. An administrator can modify the property by navigating to System PropertiesSystem. The default format is: yyyy-MM-dd.
Note:
A user can override the global date or time format with a personal preference.
Modifying the glide.sys.date_format property changes the date or time format globally. When modifying the standard date format, also verify the format using a [Validate date and time](https://www.servicenow.com/docs/access?context=c_ValidateDateAndTime&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) script. You can use the same pattern strings as the [java.text.SimpleDateFormat](https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html) class, with the following exception:
* You cannot append the 'z' character to include the time zone when adding it to a script.
* If the resulting time zone is not three characters, an Invalid Date appears error appears when you validate the script, because the Date/Time Validation Script (sys_script_validator) fails. This failure occurs even though the script debugger shows that the content of the value meets the requirement of 'g_user_date_time_format'.
{#r_FormatDateAndTimeFields__ul_hdz_s4h_p3b}
MM is months, while mm indicates minutes. The format string consists of the following abbreviations. {#r_FormatDateAndTimeFields__table_hsv_rqb_3p__entry__3}
| Field | Full form | Short form |
|-|-|-|
| Year | yyyy (4 digits) | yy (2 digits), y (2 or 4 digits) |
| Month | MMM (name or abbr.) | MM (2 digits), M (1 or 2 digits) |
| Day of Month | dd (2 digits) | d (1 or 2 digits) |
[ ]
{#r_FormatDateAndTimeFields__table_hsv_rqb_3p}
Note:
It is recommended that you use a yyyy format-based date. For example, use MM-dd-yyyy, yyyy-MM-dd, or dd-MM-yyyy.
* If your system date format is set to use the yy year format, the system considers dates 20 years later or 80 years earlier from the current date as a date in the past or future leading to an unexpected behavior.
* For example, if you set the year as 51 for 2051, the system considers the year as 1951. Similarly, if you set the year as 37 for 1937, the system considers the year as 2037.
{#r_FormatDateAndTimeFields__ul_fnm_zsf_4jb}
## Time format
An administrator can modify the glide.sys.time_format property by navigating to System PropertiesSystem. Modifying the property changes the date or time format globally. When modifying the standard time format, also verify the format using a [Validate date and time](https://www.servicenow.com/docs/access?context=c_ValidateDateAndTime&version=yokohama&pubname=yokohama-api-reference&ft:locale=en-US) script. You can use the same pattern strings as the [java.text.SimpleDateFormat](https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html) class, with the following exception: Appending 'z' to include the time zone is not supported.
The format string consists of the following abbreviations.
{#r_FormatDateAndTimeFields__table_q1g_frb_3p__entry__3}
| Field | Full form | Short form |
|-|-|-|
| Hour (1-12) | hh (2 digits) | h (1 or 2 digits) |
| Hour (0-23) | HH (2 digits) | H (1 or 2 digits) |
| Minute | mm (2 digits) | m (1 or 2 digits) |
| Second | ss (2 digits) | s (1 or 2 digits) |
[ ]
{#r_FormatDateAndTimeFields__table_q1g_frb_3p}
Add the character a to the end of the time format
string to indicate AM or PM. This option shows AM or PM whether you are using 12-hour time
(hh) or 24-hour time (HH).
The default format is: HH:mm:ss.
Note:
A user can override the global date or time format with a personal preference.
* **[Personalize the system date format](https://www.servicenow.com/docs/0rvdiecEFcEfaiD9T5ml6g)**
You can personalize the format in which date values appear in your instance.
* **[Personalize the system time format](https://www.servicenow.com/docs/y~MqHL_PP2FqhWfeZ2xUkg)**
You can personalize the format in which time values appear in your instance.
**Related reference**
* [Schedule entry fields](https://www.servicenow.com/docs/YtxbvqtSofMcS~HIBZj_cg "You can only associate a schedule entry with one schedule. The Schedule Entries related list contains the definitions of the time periods you want to include in or exclude from the schedule.")
*[\>]: and then