Knowledge Linkage to Taxonomies in Employee Center Not Showing Latest Version

[Molly KM Ops]

When I link articles to a topic in the taxonomy, I have to select a specific version (e.g., v1.0, v2.0). I will select the latest version. However, if I update the article to a new version, it will remove the article from showing in that topic because the latest version is no longer linked. I have to manually relink the article to the topics I want it linked to. This is a very manual process and takes a lot of time to relink articles every time a new version is released.

Is there a way to link the Latest version of an article to a topic in a taxonomy, so that automatically the article will always be shown in that topic even when new versions are released?

[Sajal Gupta]

@Molly KM Ops 

Once the new article is published it should automatically appear in the connected content for a topic. if it's still not appearing after publishing the article then you might be missing or disabled a business rule which automatically adds it to connected content.

Regards

Sajal

[Molly KM Ops]

What's happening, as an example, when I release a version 5.0, it will not link to the taxonomy topic, but version 4.0 continues to stay linked to the topic.

[Hiranmayee Moha]

@Sajal Gupta ...

I do have same issue. As u mentioned, the BR is active, but the article is not showing in the portal. It is available through global search & through native view. 

Kindly provide any suggestion/solution.

Thanks

Hiranmayee Mohanta

[Alexander17]

Looks like you have manual connected the article to the topic and not the knowledge category where it is in it. Correct? unfortunately the connected content is on article level on version. Once you remap to a newer version, that version will appear. We had many many many issues as we found out that for each knowledge article version a new connected content item was created. We have in some case more than 10 versions of the same article connected. This is a bug/fault in how servicenow auto update connected content in the system. In our case we have more over 45k connections over time.. what mega slow our employee center performance.