SOW ITSM: Post Washington Upgrade: "No Content to display: Please add components into the carousel."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2024 03:51 PM
Problem: I do not see the mini dashboard elements, such as the donut or the cards for the incidents, catalog tasks, etc, on the SOW landing page.
Context: I recently upgraded my temporary instance from Utah to the recent Washington release (Patch 1 Hot Fix 1).
Request: Please assist me in re-adding the elements in my current instance back into the upgraded instance—see the attached image below. The left side is the temporary (upgraded) instance, and the right is the standard dev environment exhibiting the expected behavior/functionality.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2024 07:42 PM
Hey @Xavier_Wharton,
Just checked my PDI (Washington release) and everything looks fine.
Can you check if the Service Operations Workspace is up to date? If not, try updating it and see if that fixes the issue.
Cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2024 06:48 AM
@James Chun thank you for the suggestion. Would you mind guiding me or pointing me to a resource on how to perform an update of SOW?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2024 11:56 AM
@Xavier_Whartonno worries, try the following:
- Navigate System Definition > Plugins
- Search sn_sow_itsm_cont
- There should be a result under 'Updates' tab
- Open the record and select 'Proceed to Update'
Cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2024 05:28 PM
Thank you. I tried that and updated to the new version, but I still have the same issue. All of the new features show up, but the message still displays regarding carousel and missing content.
I opened a case with Now Support. I wonder if it has anything to do with the instance being a temporary one and not the native DEV.
However, I did clone down my production instance to the temporary instance, and the Utah version looked fine.
I'll keep you updated @James Chun