- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2023 01:40 PM
Hello everyone, I'm starting to play with the Rich Content widget and editor and have a question about what are the minimum requirements to get a topic page to display in the mega menu. I have updated the taxonomy to include the topic page in question and have published a rich content item to the page, but it doesn't appear in the mega menu as an option.
I can manually navigate to the page if I copy the sys_id from the taxonomy setup and I can see the rich content displayed, but it doesn't appear in the mega menu. Is it possible to have a page with only rich content show in the mega menu, or if not, what item(s) need to be connected to the topic page for it to appear in the menu?
Thanks in advance,
Ash
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-20-2023 12:52 AM
Hi @Ashley Heath , for Topics to appear in the Mega Menu they must have connected content. So this means a Catalog Item or Knowledge Article connected to the topic.
When connected content is not present, the topic will not appear in the Mega Menu.
It is also worth noting that the Taxonomy utilises the existing User Criteria that is present on catalog items and KB articles. So if you have connected them and still see nothing, ensure there is not User Criteria doing this.
And finally, sometimes you need to log out and back in for changes to render due to caching. Another quick tip is to impersonate another user, as that immediately refreshes the assets.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-20-2023 12:52 AM
Hi @Ashley Heath , for Topics to appear in the Mega Menu they must have connected content. So this means a Catalog Item or Knowledge Article connected to the topic.
When connected content is not present, the topic will not appear in the Mega Menu.
It is also worth noting that the Taxonomy utilises the existing User Criteria that is present on catalog items and KB articles. So if you have connected them and still see nothing, ensure there is not User Criteria doing this.
And finally, sometimes you need to log out and back in for changes to render due to caching. Another quick tip is to impersonate another user, as that immediately refreshes the assets.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-14-2023 08:07 AM
Can either of you share some words of wisdom? After cloning the OOB Employee Taxonomy we expected to be able to see the parent topics in the mega menu. After some research and trial and error, The mega menu is still blank.
I have my Employee (Clone) taxonomy added to the Employee Center Service Portal.
Navigation to All>Content Taxonomy>Topics
Select IT(Parent)- Connected Content shows 19 objects and Child topics listed = 5.
Is there a step I have missed?
You time is appreciated.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-20-2023 06:37 AM
Hey @KKrabbenhoft
If you have the taxonomy correctly defined in your Employee Center portal record there is only two reasons as to why the mega menu would be blank
1) Topics do not have any connected content (which doesn't look like the case here)
2) User Criteria is in place, which is removing the items from the logged in user. User Criteria is used to define who can see what, so if all the items from a topic are not available to the logged in user, they will be hidden.
Also make sure if you've just connected it, to impersonate another user or log out and back in. Caching is a pain and doesnt always render new changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-20-2023 06:07 AM
Thanks for the information, Dan. I had a feeling that we needed to connect at least one article or catalog item but wasn't sure if there was a trick that I was missing. I also discovered the caching issue when we created a previous topic page and quickly impersonating a user and ending the impersonation does the trick every time. 🙂