Daylight savings time offset is inconsistent for GlideTime using `getDisplayValue` and `getDisplayValueInternal`DescriptionWhen running a script with GlideTime and using `getDisplayValue` and `getDisplayValueInternal` results are different because DST (Daylight Savings Time) offset is applied to one but not another. When running a script with GlideDateTime and using `getDisplayValue` and `getDisplayValueInternal` results do seem to account for DST offset, however when you use 'GlideDateTime.getTime()' to only show the time, DST offset is now no longer accounted for. Script var a = new GlideTime();var b = new GlideDateTime();gs.print("GlideTime");gs.print(a.getDisplayValueInternal());gs.print(a.getDisplayValue());gs.print("GlideDateTime");gs.print(b.getDisplayValueInternal());gs.print(b.getDisplayValue()); gs.print("GlideDateTime.getTime()");gs.print(b.getTime().getDisplayValueInternal());gs.print(b.getTime().getDisplayValue()); Time ran: 06:58:08 PST Output *** Script: GlideTime*** Script: 06:58:08*** Script: 05:58:08*** Script: GlideDateTime*** Script: 2019-03-20 06:58:08*** Script: 2019-03-20 06:58:08*** Script: GlideDateTime.getTime()*** Script: 05:58:08*** Script: 05:58:08 Notice how the first results under the line "*** Script: GlideTime" are off from each-other by one hour. One is showing DST added and the other is not. Also notice how a GlideDateTime does seem to factor DST properly, but when doing GlideDateTime.getTime() it now does not seem to factor DST anymore. ResolutionUsing GlideTime with 'getDisplayValueInternal()' will calculate with DST offset considered, and also using GlideDateTime with 'getDisplayValueInternal()' or 'getDisplayValue()' also calculate with DST offset factored in. Additional InformationServiceNow Developers - GlideDateTime ServiceNow Developers - GlideTime