Contents ServiceNow Platform Previous Topic Next Topic Time zones Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Time zones All times are stored in Coordinated Universal Time (UTC). They are displayed globally based on the system time zone, but are displayed to users in their local time zone according to user preferences. Time zone representation Time zones that have the Country/City format are primary time zone IDs. Other time zone IDs are links to the primary time zone. For example, US/Pacific is a link to the America/Los_Angeles time zone. Both America/Los_Angeles and US/Pacific represent Pacific Standard Time with the same zone offset and Daylight Savings Time (DST) schedule. Other than the representation, there is no impact on date and time functionality. In the absence of a default time zone for the user or the system, JVM reads default time zone information from the machine. Depending on how the machine is configured, it might return the Country/City or link, for example, US/Pacific or America/Los_Angeles. Administrators should configure their system with a default timezone “glide.sys.default.tz” to avoid system dependencies. Daylight Saving Time In general, if a time zone is specified based on location (for example, America/Los Angeles), the system automatically adjusts for daylight saving time. If a time zone is specified based on the name of a time zone (for example, GMT), it does not adjust. User preferences Once the System Time Zone is defined, users can also select their own time zone from their user form, accessed through Self-Service > My Profile. The System default appears as System ([name of the default time zone]). For example, if the System time zone is America/Los_Angeles, the user seesSystem (America/Los Angeles). Time zones in email notifications The date and time stamp of a notification uses the system time zone and not the time zone of any recipient. The property glide.email.append.timezone in System Properties > Email controls whether to append the time zone. If true, the system time zone of the instance is appended to any dates or date/times in outbound email messages (for example, 2010-07-02 04:01:14 PST). Time zones in service level agreements Service level agreements have different options for which time zone to use. To set a time-zone for SLAs, navigate to Service Level Management > SLA Properties and locate the following property: Figure 1. Time zone for service level agreements Some special considerations: If The caller's time zone is selected, unpredictable behavior can occur if the caller does not have a time zone defined. If The SLA definition's time zone is selected, the time zone must be manually defined on the SLAs form. Time zone in scripting When scripting on the server, there are several GlideSystem Date and Time Functions used to get time values. For more information about specific methods and to learn the format in which each returns the requested time, see the GlideSystem API. Enhancements DST enhancement requires that reports and queries observe daylight saving time rules. The changes affect trend charts, line charts, and filters using the "trend on" operation. Time zone changer The time zone changer is active by default. Users can change their time zone in the system settings (the gear on the top right of the banner). Change the time zone choice listWherever users have a choice of time zone, the choices are populated using the Time Zone choice list on the User [sys_user] table. Not all time zones appear by default.Change a time zone in a scheduled reportBy default, scheduled reports use the time zone of the user who runs them (the user in the Run As field) to evaluate the query parameters. You are able to change this time zone.Change a time zone in a scheduled data importBy default, scheduled data imports are run using the time zone of the user who creates them. However, there is a way to manually specify the time zone for the import.Set a system time zoneHow to set a default time zone for calendars and users.Time zones in SLAsService Level Agreements have a number of options of which time zone to use.Related TasksSet a system time zoneChange the time zone choice listChange a time zone in a scheduled reportChange a time zone in a scheduled data import On this page Send Feedback Previous Topic Next Topic
Time zones All times are stored in Coordinated Universal Time (UTC). They are displayed globally based on the system time zone, but are displayed to users in their local time zone according to user preferences. Time zone representation Time zones that have the Country/City format are primary time zone IDs. Other time zone IDs are links to the primary time zone. For example, US/Pacific is a link to the America/Los_Angeles time zone. Both America/Los_Angeles and US/Pacific represent Pacific Standard Time with the same zone offset and Daylight Savings Time (DST) schedule. Other than the representation, there is no impact on date and time functionality. In the absence of a default time zone for the user or the system, JVM reads default time zone information from the machine. Depending on how the machine is configured, it might return the Country/City or link, for example, US/Pacific or America/Los_Angeles. Administrators should configure their system with a default timezone “glide.sys.default.tz” to avoid system dependencies. Daylight Saving Time In general, if a time zone is specified based on location (for example, America/Los Angeles), the system automatically adjusts for daylight saving time. If a time zone is specified based on the name of a time zone (for example, GMT), it does not adjust. User preferences Once the System Time Zone is defined, users can also select their own time zone from their user form, accessed through Self-Service > My Profile. The System default appears as System ([name of the default time zone]). For example, if the System time zone is America/Los_Angeles, the user seesSystem (America/Los Angeles). Time zones in email notifications The date and time stamp of a notification uses the system time zone and not the time zone of any recipient. The property glide.email.append.timezone in System Properties > Email controls whether to append the time zone. If true, the system time zone of the instance is appended to any dates or date/times in outbound email messages (for example, 2010-07-02 04:01:14 PST). Time zones in service level agreements Service level agreements have different options for which time zone to use. To set a time-zone for SLAs, navigate to Service Level Management > SLA Properties and locate the following property: Figure 1. Time zone for service level agreements Some special considerations: If The caller's time zone is selected, unpredictable behavior can occur if the caller does not have a time zone defined. If The SLA definition's time zone is selected, the time zone must be manually defined on the SLAs form. Time zone in scripting When scripting on the server, there are several GlideSystem Date and Time Functions used to get time values. For more information about specific methods and to learn the format in which each returns the requested time, see the GlideSystem API. Enhancements DST enhancement requires that reports and queries observe daylight saving time rules. The changes affect trend charts, line charts, and filters using the "trend on" operation. Time zone changer The time zone changer is active by default. Users can change their time zone in the system settings (the gear on the top right of the banner). Change the time zone choice listWherever users have a choice of time zone, the choices are populated using the Time Zone choice list on the User [sys_user] table. Not all time zones appear by default.Change a time zone in a scheduled reportBy default, scheduled reports use the time zone of the user who runs them (the user in the Run As field) to evaluate the query parameters. You are able to change this time zone.Change a time zone in a scheduled data importBy default, scheduled data imports are run using the time zone of the user who creates them. However, there is a way to manually specify the time zone for the import.Set a system time zoneHow to set a default time zone for calendars and users.Time zones in SLAsService Level Agreements have a number of options of which time zone to use.Related TasksSet a system time zoneChange the time zone choice listChange a time zone in a scheduled reportChange a time zone in a scheduled data import
Time zones All times are stored in Coordinated Universal Time (UTC). They are displayed globally based on the system time zone, but are displayed to users in their local time zone according to user preferences. Time zone representation Time zones that have the Country/City format are primary time zone IDs. Other time zone IDs are links to the primary time zone. For example, US/Pacific is a link to the America/Los_Angeles time zone. Both America/Los_Angeles and US/Pacific represent Pacific Standard Time with the same zone offset and Daylight Savings Time (DST) schedule. Other than the representation, there is no impact on date and time functionality. In the absence of a default time zone for the user or the system, JVM reads default time zone information from the machine. Depending on how the machine is configured, it might return the Country/City or link, for example, US/Pacific or America/Los_Angeles. Administrators should configure their system with a default timezone “glide.sys.default.tz” to avoid system dependencies. Daylight Saving Time In general, if a time zone is specified based on location (for example, America/Los Angeles), the system automatically adjusts for daylight saving time. If a time zone is specified based on the name of a time zone (for example, GMT), it does not adjust. User preferences Once the System Time Zone is defined, users can also select their own time zone from their user form, accessed through Self-Service > My Profile. The System default appears as System ([name of the default time zone]). For example, if the System time zone is America/Los_Angeles, the user seesSystem (America/Los Angeles). Time zones in email notifications The date and time stamp of a notification uses the system time zone and not the time zone of any recipient. The property glide.email.append.timezone in System Properties > Email controls whether to append the time zone. If true, the system time zone of the instance is appended to any dates or date/times in outbound email messages (for example, 2010-07-02 04:01:14 PST). Time zones in service level agreements Service level agreements have different options for which time zone to use. To set a time-zone for SLAs, navigate to Service Level Management > SLA Properties and locate the following property: Figure 1. Time zone for service level agreements Some special considerations: If The caller's time zone is selected, unpredictable behavior can occur if the caller does not have a time zone defined. If The SLA definition's time zone is selected, the time zone must be manually defined on the SLAs form. Time zone in scripting When scripting on the server, there are several GlideSystem Date and Time Functions used to get time values. For more information about specific methods and to learn the format in which each returns the requested time, see the GlideSystem API. Enhancements DST enhancement requires that reports and queries observe daylight saving time rules. The changes affect trend charts, line charts, and filters using the "trend on" operation. Time zone changer The time zone changer is active by default. Users can change their time zone in the system settings (the gear on the top right of the banner). Change the time zone choice listWherever users have a choice of time zone, the choices are populated using the Time Zone choice list on the User [sys_user] table. Not all time zones appear by default.Change a time zone in a scheduled reportBy default, scheduled reports use the time zone of the user who runs them (the user in the Run As field) to evaluate the query parameters. You are able to change this time zone.Change a time zone in a scheduled data importBy default, scheduled data imports are run using the time zone of the user who creates them. However, there is a way to manually specify the time zone for the import.Set a system time zoneHow to set a default time zone for calendars and users.Time zones in SLAsService Level Agreements have a number of options of which time zone to use.Related TasksSet a system time zoneChange the time zone choice listChange a time zone in a scheduled reportChange a time zone in a scheduled data import
