Time zone issue in Visitor registration form - Support and Troubleshooting

Time zone issue in Visitor registration form Issue .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } In visitor registration form we have noticed that when we select a location from IST time zone in the form the displayed time zone(Asia/Kolkata) in the UI is different from backend table for the respective selected location. We have replicated this in the PDI.

Where as in reservation form the time zone displayed in the UI is as expected. Why is the behavior different in both forms? The expectation is the configured time zone should be displayed same as reservation form in the visitor registration form.

Steps to Reproduce Navigate to All → Register Visitors Open the Visitor Registration form Ensure the user/location time zone is configured for IST Select a location configured with IST time zone Observe the displayed time zone value Expected Result The form should display the configured time zone abbreviation (for example, IST ) similar to the Reservation form.

Actual Result The form displays the raw IANA time zone value ( Asia/Kolkata ).

Release .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } -

Cause .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Known product defect PRB2015463 in the Visitor module where the UI renders the backend IANA time zone value instead of the formatted display label.

Resolution .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Temporary Workaround

Engineering has validated the permanent fix on the instance and confirmed that the issue is resolved after updating the following two components in sn_wsd_core:

Angular Provider — wsdScheduleEditorUiComponent Add IANA → timezone abbreviation mapping Introduce timezoneDisplay using: getTimezoneDisplayLabel(scope.timezone) Ensure timezoneDisplay is updated on initialization and on $watch('timezone')

UI Macro — wsd-schedule-editor-ui-component-template Update binding from:

To proceed with the correct fix, could you please follow the steps below in your instance?

Step 1: Update Angular Provider

Navigate to: sp_angular_provider.do?sysparm_query=name=wsdScheduleEditorUiComponent

Then:

Open the record Edit the Script field Inside wsdScheduleEditorUiComponent(...), add the following block before the return statement: var IANA_TO_TZ_ABBR = { 'Australia/Darwin': 'ACT', 'Australia/Sydney': 'AET', 'America/Argentina/Buenos_Aires': 'AGT', 'Africa/Cairo': 'ART', 'America/Anchorage': 'AST', 'America/Sao_Paulo': 'BET', 'Asia/Dhaka': 'BST', 'Africa/Harare': 'CAT', 'America/St_Johns': 'CNT', 'America/Chicago': 'CST', 'Asia/Shanghai': 'CTT', 'Africa/Addis_Ababa': 'EAT', 'Europe/Paris': 'ECT', 'America/Indiana/Indianapolis': 'IET', 'Asia/Kolkata': 'IST', 'Asia/Tokyo': 'JST', 'Pacific/Apia': 'MIT', 'Asia/Yerevan': 'NET', 'Pacific/Auckland': 'NST', 'Asia/Karachi': 'PLT', 'America/Phoenix': 'PNT', 'America/Puerto_Rico': 'PRT', 'America/Los_Angeles': 'PST', 'Pacific/Guadalcanal': 'SST', 'Asia/Ho_Chi_Minh': 'VST', };

function getTimezoneDisplayLabel(ianaId) { return ianaId ? (IANA_TO_TZ_ABBR[ianaId] || ianaId) : ''; } 4.Find the line that initializes scope.timezone (inside the link function):

scope.timezone = scope.timezone || '';

Add this line right after it:

scope.timezoneDisplay = getTimezoneDisplayLabel(scope.timezone);

5.Find the scope.$watch('timezone', ...) handler. Inside the watch callback, add the same line:

scope.timezoneDisplay = getTimezoneDisplayLabel(scope.timezone);

6.Save the record.

Record 2: UI Macro — wsd-schedule-editor-ui-component-template

Navigate to: sys_ui_macro.do?sysparm_query=nameLIKEschedule-editor-ui-component-template Open the record and edit the XML field Find this line: ${gs.getMessage('Location timezone')}: { {timezone}}

Change it to:

${gs.getMessage('Location timezone')}: { {timezoneDisplay || timezone}}

4.Save the record. 5.Flush the cache: navigate to cache.do and confirm.