Kb_knowledge_create

Madhan12
Tera Contributor

On navigating to create new on Knowledge landing on the page

https://instnace name.service-now.com/now/nav/ui/classic/params/target/kb_knowledge_create.do%3F%26s...

 

on the new version of page after selecting "NEXT" the page is idle and not going to template selector.

8 REPLIES 8

@Sohail Khilji 

1000023292.jpg

 as highlighted in the screenshot on clicking on next no action, it's idle.

Tried by repairing the plugins. No change

Hi @Madhan12 ,

 

As i stated in above post you need to enable the (Knowledge Management Advanced (com. snc. knowledge_advanced)) plugin in order to get the Article template.

 

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.


Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------

j_s_1
Tera Contributor

I also have this issue in several SN instances. The Knowledge Management Advanced plugin is active in all the instances. We have made no recent changes to the knowledge management configuration, but creation of knowledge articles started failing about 3 days ago.

 

Repairing the Knowledge Management Advanced plugin had no effect. 

Looking in the browser console, there is an exception thrown for an empty Try block for kb_knowledge_create.do on line 368, position 139

Console exception.png

Console - empty try.png

j_s_1
Tera Contributor

I found a fix for my situation. Line 3 HTML of the kb_knowledge_create UI page was updated from:

 

<g:requires name="scripts/angular_1.5.11/angular.min.js" inline="true" position="last"/>

 

to

 

<g:requires name="scripts/angular_1.5.11/angular.min.js" position="last"/>

 

 
This line was updated in Washington DC Patch 7a, but was skipped in my instances. 
 
Reverting line 3 to be the same as the base ServiceNow fixed the issue in my case.