- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2023 02:16 AM - edited 06-23-2023 02:19 AM
Good morning,
Currently testing the latest ServiceNow family release (Utah Patch 4) and came across a minor problem.
When you schedule an in-person appointment with an engineer, you receive an info message at the top of the portal confirming the appointment has been booked but the time always displays 12:00am to 12:00am no matter what time is selected.
Nothing has been updated in terms of the Widget, everything is OOB.
I have checked this in our other instances currently on SD Patch 10 and works fine.
Checking the appointment record, it does show the correct times, so it is a minor problem but could cause confusion with our users.
Has anyone else seen this problem? any ideas?
Kind Regards
Ashley
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2023 02:36 AM
Good morning,
ServiceNow has confirmed this is related to a problem: PRB1669804
No eta on a fix at the moment
Shortcut URL:
Kind Regards
Ashley
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2023 02:40 AM
Hi @Ashley ,
Hope you are doing great.
I didn't encountered issue , but to address this issue, I recommend the following steps:
Double-check the configuration settings related to the appointment widget, ensuring that all the necessary fields and properties are correctly set.
Compare the configuration of your current instance (Utah Patch 4) with the working instances (SD Patch 10) to identify any discrepancies or missing settings that might be causing the incorrect time display.
Examine the system logs and error messages related to the appointment functionality to identify any specific error or warning messages that could shed light on the issue.
If you are unable to identify a solution through the above steps, consider raising a support ticket with ServiceNow, providing them with detailed information about the problem. Include specific steps to reproduce the issue and any relevant logs or error messages you have encountered.
Regards,
Riya Verma
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2023 04:09 AM - edited 06-23-2023 04:10 AM
Hi @Riya Verma
Thank you for replying so quickly,
I have logged a HI ticket with ServiceNow, I saw quite a few differences between our SD release and Utah upgrade which are all ServiceNow OOB updates so shouldn't be any reason why they shouldn't work.
I will circle back and update this thread once we figure out whats going on so other people can benefit from it.
Kind Regards
Ashley
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2023 02:36 AM
Good morning,
ServiceNow has confirmed this is related to a problem: PRB1669804
No eta on a fix at the moment
Shortcut URL:
Kind Regards
Ashley
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2024 07:40 AM
Hi Ashley,
I'm experiencing the same issue, I'm unable to see the problem. Has this been fixed?