- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2020 09:01 AM
I have a knowledge base populated with articles that were migrated from another instance of ServiceNow that was running a different release level. (Copied from an instance running Orlando to an instance running New York) ... Long Story.
When knowledge base articles are updated, a new version is created and the Workflow for all previous versions is set to Draft and the Workflow in the record shows as "outdated" - See Screen Shots below
The issue I'm having is when I search for the KBA, the article is found, but when I click on the link to open the article, it shows the first article created with the outdated workflow? (Images Below)
How do I get ServiceNow to display the most recent "Published" article.
LIST OF KBA'S
WORKFLOW SHOWS AS OUTDATED
KBA Search
Article Found
Article Displayed
Solved! Go to Solution.
- Labels:
-
Knowledge Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2020 10:51 AM
The cause of the issue was the absence of the Knowledge Management Advanced plugin.
The source instance had the Knowledge Management Advanced plugin installed. The target instance did not. Once the plugin was installed, the search capability worked as desired.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2020 11:16 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2020 02:47 PM
Not sure if this is correct but the problem may be caused by knowledge base version difference between New York and Orlando.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0713200
It may be better to contact HI support. They are able to look into the instance and provide quicker solution to cases like this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2020 10:51 AM
The cause of the issue was the absence of the Knowledge Management Advanced plugin.
The source instance had the Knowledge Management Advanced plugin installed. The target instance did not. Once the plugin was installed, the search capability worked as desired.