Notifications

1089 views

Description

GlideDate API does not function correctly since Madrid, not honoring getDisplayValueInternal().

Steps to Reproduce

1. Login as system administrator in a Madrid instance.

2. Set your admin's timezone different than the system timezone.

3. Make sure you are still logged on with a different timezone and run the script below:
var gd = GlideDate();
gs.print("gd : " + gd);
gs.print("internal: " + gd.getDisplayValueInternal());
var gdt = new GlideDateTime(gd);
gs.print("GDT Internal: " + gdt.getDisplayValueInternal());
gs.print("GDT User: " + new GlideDateTime());

Example results for TimeZone HongKong, where the GMT date is different than user's timezone date:

- Madrid Patch 2:
*** Script: gd : 2019-05-01
*** Script: internal: 2019-05-01
*** Script: GDT Internal: 2019-05-02 04:43:42
*** Script: GDT User: 2019-05-01 20:43:42

- London Patch 7:
*** Script: gd : 2019-05-01
*** Script: internal: 2019-05-02
*** Script: GDT Internal: 2019-05-02 04:45:47
*** Script: GDT User: 2019-05-01 20:45:47

Workaround

This problem is under review and targeted to be fixed in a future release. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form.


Related Problem: PRB1341509

Seen In

SR - ITOM - Discovery and Service Mapping - 201908
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3

Fixed In

Madrid Patch 9
New York Patch 3 Hot Fix 2
New York Patch 4
Orlando

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-07-30 04:35:24
Published:2019-07-10