- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2024 10:59 AM
Hello everyone!
Running into an odd issue with a notification email.
During the implementation step of our Change Management process, we have a notification that notifies our users that their change is approved, and to work on their implementation task. This email contains relevant change info (Type, Category, Planned Start/End Dates, etc). However, the CAB date, planned start, and planned end dates are incorrect, and seem to be offset by exactly 5 hours. I've reviewed the email script used to generate the email and see it is using the following for the date variables:
Email information:
I have verified our instance of SN is configured with our time zone. Any thoughts or insight on how to resolve this is appreciated!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2024 01:18 PM
Hi Peter,
Try
gr.change_request.start_date.getDisplayValue()
instead of
gr.change_request.start_date
JP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2024 12:55 PM
@Peter P You are most likely not getting the Datetime values in local time (for the given user) when constructing the email so it will by default show whatever timezone is defined by the system. When impersonating a user, the times will reflect what the user has defined as their time zone.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2024 01:18 PM
Hi Peter,
Try
gr.change_request.start_date.getDisplayValue()
instead of
gr.change_request.start_date
JP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2024 01:24 PM
Amazing, this solved it! Always foiled by getDisplayValue()!
Thanks JP!