Knowledge Blocks not displaying correctly

Thedavisrun
Mega Expert

We are just implementing K Blocks and are running into an issue with how they are displayed in the actual KBase.

They just display a block but not the text etc.  See below for recreation steps. 

Steps to recreate. 
1. Create a knowledge Block. 
2. Create an Article 
3. Add the Knowledge Block created to the article. 
4. Publish the article. 
5. Go to the HR portal and Find the Article. 
6. Notice the Article View is incorrect. It seems the back-end view from ServiceNow. As a result, the Knowledge Blocks are displayed instead of the text that belongs to the Knowledge Block (see screenshot 1). 

Screenshot1
find_real_file.png
EXPECTED BEHAVIOR: When the user goes to the HR Portal and click in the article, he should be able to see the text that comes from the Knowledge Blocks. 

*If you go to the back-end and open the article, there is one option to preview how it looks with the Knowledge Blocks. When we click there (See screenshot 2) the correct view is displayed (Screenshot 3). 

Screenshot2

find_real_file.png

Screenshot3

find_real_file.png

1 ACCEPTED SOLUTION

Thedavisrun
Mega Expert

It turned out this was a problem with the KB article display widget as we had it customized.  the only way to fix was to go back to the out of the box widget. 

View solution in original post

7 REPLIES 7

Alex Sheehy
Kilo Contributor

having the same issue in Quebec but we are using the OOTB widget and its still not working - any ideas here?

Good Morning,

 

Did you ever get this resolved? we're seeing the same issue with the OOB widget on Utah

 

Kind Regards

 

Ashley

Tonyskin
Tera Contributor

We are having the same issue on Tokyo with the OOTB widget.  Is there something we need to add somewhere to get it to display more than just the KBB number and title when viewing it on the portal?  I know that if the article type is not set to HTML, when you go look at the article, it will not really link the KBB so it just shows the number and title, but we got past that part.  With our environment, it just doesn't show on the search results screen properly (using AI Search if that makes a difference.)