Walk-up Experience - Operational Hours not showing Time Zone with Standard Code - Support and Troubleshooting

Walk-up Experience - Operational Hours not showing Time Zone with Standard Code Issue Out of the Box, the Operational Hours in the About this location section of the Walk Up Check-in portal page ( walkup_online_checkin ) shows the Time Zone in the UTC Offset format (i.e. +0530, +08, etc.).

This article explains how to display it in the String format (i.e. IST, MYT, etc.)

Release All

Cause There are two different scenarios with two separate causes and solutions.

Scenario 1 - India location displaying +0530

If, for example, the selected location is for India , the OOB time format that needs to be used is Asia/Kolkata . If this choice is inactive on the instance, the timezone format would be displayed as +0530 .

In this case, the issue might be that the Asia/Kolkata timezone is inactive on the instance: https://instance_name.service-now.com/sys_choice.do?sys_id=a4938a59c6112278002c91038db3affb

Scenario 2 - Malaysia location displaying +08

If, for example, the selected location is for Malaysia , the OOB time format that needs to be used is Asia/Kuala_Lumpur .

In this case, the behaviour is expected.

The displayed widget is Online check-in experience : https://instance_name.service-now.com/nav_to.do?uri=sp_widget.do?sys_id=f84cfc133b7303001d132c2b54efc476

The definition for the timezones and their formats comes from moment-timezone-with-data-2010-2020-v0.5 dependency: https:// instance_name .service-now.com/nav_to.do?uri=sp_dependency.do?sys_id=db6689c1cb11120000f8d856634c9c3b

which, in the end, uses the open source JavaScript library momentjs : https://momentjs.com/timezone/

In momentjs , the Malaysian Timezone does NOT have an abbreviation of MYT but rather +08 . ServiceNow platform is simply using what is coming from momentjs .

The reason that Asia/Kolkata works as expected after activating the choice is that Asia/Kolkata has an abbreviation of IST defined in the momentjs open source library, unlike Asia/Kuala_Lumpur.

Resolution The solution to Scenario 1 is to activate the Asia/Kolkata timezone sys_choice. More details on how to activate Timezones can be found here:

Time zones Change the time zone choice list

---

As mentioned above, Scenario 2 is working as expected since ServiceNow has no control on the data defined in open source library momentjs.

However, the timezone format is being used in Angular Provider formatWalkUpSchedule https://instance_name.service-now.com/nav_to.do?uri=sp_angular_provider.do?sys_id=b413345153041300c6bfddeeff7b12b6

function createTimeSpan(start, end) { return { fStart: start, fEnd: end, start: start.format('h:mma'), end: end.format('h:mma (z)') }; } A possible workaround involves customizing the above Angular Provider formatWalkUpSchedule based on examples found on the momentjs documentation itself: https://momentjs.com/timezone/docs/#/using-timezones/formatting/

1. In Angular Provider formatWalkUpSchedule , add the following function to override the default moment.fn.zoneName function. You can specify whichever timezone format you want to override and can add more abbreviations as needed or override them with whatever string you like. In below example, we are overriding: - +08 with MYT - + 07 with Asia/Bangkok

moment.fn.zoneName = function(){ var abbrs = { '+08' : 'MYT', '+07' : 'Asia/Bangkok' };

var abbr = this.zoneAbbr(); return abbrs[abbr] || abbr; }

2. On the same Angular Provider formatWalkUpSchedule , in function createTimeSpan() , replace:

end: end.format('h:mma (z)') with

end: end.format('h:mma (zz)') After above changes, the timezone for the Malaysia location would look like this:

NOTE that the above would be considered a custom implementation and would not be supported by ServiceNow.