How to auto publish knowledge article created from incident when incident is closed.

[E-E]

Hi, 
When creating a knowledge article from incident, the article will be saved as Draft when the incident is closed, and in order to publish we need to go to the article record and press publish.

Instead, I am looking for a way to directly publish the article when the incident is closed. (skipping Draft, Review stage. )
Do I have to create a new Knowledge Base and create a new flow or is there some other way to do this? 
Would appreciate it if you could provide the steps for this as I do not have much experience on those functions.
Thanks.

[Dr Atul G- LNG]

Hi @E-E 

Greetings!!

1 point, it is not recommended approach to publish the article immediate as there are chance that you need to update the Meta data and other information in KB which is not coming from Incident and you need to manually entered and there are case that in KB few more information need to updated / formatted to make it presentable , so my suggestion do it manually.

But still you want to do , yes create New Base and flow and that flow must be go from draft to publish.

Also still curious to know, what is the business case for this?

[E-E]

Hi @Dr Atul G- LNG 
Thanks for your reply. 
Our client wants to make sure all closed incidents are stored as knowledge so wants to automate the process. 
Could you provide me a bit more information on how to create the workflow that goes Draft to Published? I'm new to workflow and struggling to get it right.
Thank you. 

[Dr Atul G- LNG]

Hi @E-E 

Please have a look . You can also do with help of Business Rule as well. 

https://youtu.be/F6w0jRLyBuw

[Sandeep Rajput]

@E-E Please create a business rule on incident table with following configuration.

Here is the script 

(function executeRule(current, previous /*null when async*/) {

	// Add your code here
	var relatedKBArticle = new GlideRecord('m2m_kb_task');
	relatedKBArticle.addQuery('task',current.getValue('sys_id'));
	relatedKBArticle.query();
	if(relatedKBArticle.next()){
		global.KnowledgeUIAction().publish(relatedKBArticle.kb_knowledge);
	}

})(current, previous);

Hope this helps.