Question to Knowledge Management v3 Homepage deprecation

ehgebla
Giga Guru

Hey community,

I'll get straight to the point.

I guess we all have read due to ServiceNow Communications by now that v3 will be no longer be supported in the future.
However, my question is; How can I check if my knowledge base here is still v3 or not?
Is there anything I can check?
E.g. if I go to the KB Suffix in Portal, I do SEE all my articles and knowledge bases. But Portal > Knowledge Bases is completely empty for me.
What can I do to check what exactly I need to do? How can I check if all my articles are eligible. Where is the documentation that shows how to migrate articles properly to the new knowledge base?

The issue is that our instance got implemented by a ServiceNow partner, however, we are taking care of it now as good as we can. Sorry to say but the documentations of ServiceNow on how to migrate etc are not really helpful.

I'll be happy for every answer you can give me, since I am going in circles it seems.

Thank you!

Regards

Elena

1 ACCEPTED SOLUTION

Thanks @ehgebla ,

 

I could be wrong, but did you mean that the Knowledge Management v3 homepage will be deprecated not the knowledge base?

Starting with the Washington DC release, the Knowledge Management v3 homepage (com.snc.knowledge3) is being prepared for future deprecation. It will be hidden and no longer activated on new instances but it will continue to be supported. The Knowledge Management Service Portal provides the latest experience for this functionality

 

By the looks of it, the Knowledge Management SP will still provide the same capability so it won't be an issue. Also, have a look at this article - 

https://www.servicenow.com/community/knowledge-managers/what-is-knowledge-management-v3-homepage-of-...

There is a good video in a comment added by a ServiceNow employee.

 

If you are still struggling with this, raising a Support case would be good as well.

 

Thanks

View solution in original post

7 REPLIES 7

Thanks @ehgebla ,

 

I could be wrong, but did you mean that the Knowledge Management v3 homepage will be deprecated not the knowledge base?

Starting with the Washington DC release, the Knowledge Management v3 homepage (com.snc.knowledge3) is being prepared for future deprecation. It will be hidden and no longer activated on new instances but it will continue to be supported. The Knowledge Management Service Portal provides the latest experience for this functionality

 

By the looks of it, the Knowledge Management SP will still provide the same capability so it won't be an issue. Also, have a look at this article - 

https://www.servicenow.com/community/knowledge-managers/what-is-knowledge-management-v3-homepage-of-...

There is a good video in a comment added by a ServiceNow employee.

 

If you are still struggling with this, raising a Support case would be good as well.

 

Thanks

Hi James,

this gave me a little bit light into my darkness, you seem to be right! It seems the knowledge base per se is not going to be set to be deprecated, but rather just the homepage for agents. So all articles and also everything setup in employee portal shall be the same, I suppose.
Only thing that changes is the homepage used by agents, I guess. I wonder if this also means any changes for our knowledge manager on how they approve articles and stuff.

I don't really get why, though. Sure, the filtering options might be a bit better but it's so much more user unfriendly in my opinion. Also they took the option to "Import articles" out of a DOC, which is something like a Must-have for us. I hope they will implement that in the future as well, until the old view will be deprecated later on.
(https://docs.servicenow.com/bundle/vancouver-servicenow-platform/page/product/knowledge-management/r...)

Regards

Elena

Hi @ehgebla ,

 

Good to hear that you are less concerned 🙂

 

In regards to the 'Import articles' option, can you use one of the methods listed here?

https://www.servicenow.com/community/knowledge-management-articles/options-for-importing-external-ar...

I believe the functionality is still there, it just means it will be located somewhere else when the homepage is deprecated.

 

I am not an employee of ServiceNow and cannot comment too much on why it's being deprecated but my theory is that the homepage is using a legacy or old framework for its UI. As ServiceNow is transitioning to the Next Experience Framework, this might be one of the necessary steps. Who knows, they might provide a much better UI in the future, fingers crossed. 

 

But if you think some of the functionalities being deprecated are critical, feel free to submit your ideas through Idea Portal.

 

Thanks!