- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-14-2022 09:09 AM
I was really pleased to see the addition of a portal 'favourites list' for knowledge articles, in the Rome release. It's a really useful way for customers to bookmark specific articles, rather than search for them each time.
However, in testing, if you have version control activated, I've noticed if an article is updated, the previous (outdated) version remains in the favourites widget, meaning the hyperlink takes the customer to an old version. The only way to add the new version as a favourite is to navigate to that new version and click on the Star icon, then remove the old one. Very frustrating.
Has anyone found a way to configure this so the widget is updated to show only the latest version? Other widgets (e.g. Most Read) do this OOTB, so I cant understand the logic in this one not doing that. With version control in place, why would you direct customers to old versions?
The only documentation I can find on the subject is pretty brief: https://docs.servicenow.com/bundle/rome-servicenow-platform/page/build/service-portal/task/create-a-...
Thanks in advance for any hints.
Barry.
Solved! Go to Solution.
- Labels:
-
Knowledge Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-20-2022 08:28 AM
Hi All,
I did as Lucas suggested and raised this with support, who directed me to this KBA:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1116810
It seems the issue is a bug, as opposed to a design flaw (or both?).
Anyway, I'll close down the idea I raised, and suggest any interested parties subscribe to the KBA for updates.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-20-2022 08:28 AM
Hi All,
I did as Lucas suggested and raised this with support, who directed me to this KBA:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1116810
It seems the issue is a bug, as opposed to a design flaw (or both?).
Anyway, I'll close down the idea I raised, and suggest any interested parties subscribe to the KBA for updates.