Knowledge Publish Workflow Creation Help

dadams3
Tera Contributor

Good Timezones, Everyone! 

 

Hope you are doing well! I've been tasked with creating a new workflow for the Knowledge Base Approval Publish Workflow and could use some help. I would like to have it act as it does out of box with one difference: when a Knowledge Base article is created, rather than it being created as a draft, it would be sent for approval instantly (rather than needing to click request in draft. Yet, I've been struggling to make the changes like for like to how it is within the Workflow Editor within Flow Designer. 

 

Has anyone done this within their own instance and had success with the conversion that could offer a place to start? Any help would be greatly appreciated. Thank you for your time!

2 ACCEPTED SOLUTIONS

Robbie
Kilo Patron
Kilo Patron

Hi @dadams3,

 

Whilst I understand the question and perhaps the request to avoid the extra step or click, can I ask to exercise a little caution here and check the why, and also perhaps add some boundaries around this, for example, restricting this to a certain Knowledge Base, or perhaps role, or other suitable criteria. This is exactly what logic is built into the 'Publish' button.

 

The reason why the Publish button is required is because there is a very low percentage of Articles that are written on initial creation which don't require a second read through or review from the author before sending for formal review and approval.

 

Taking on board what I've mentioned above, in order to answer your question directly, if you still want to go ahead (and you've factored in and restricted by Knowledge bqase etc), this can be achieved relatively easily by the introduction of a Business Rule that simply calls the same call to the workflow as the 'Publish' button - see below.

I still however want to advise caution and thought here and advise against it unless restricted.

 

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.


Thanks, Robbie

 

Screenshot 2024-07-26 at 17.32.13.pngScreenshot 2024-07-26 at 17.33.10.png

 

Business Rule Code:

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

	gs.addInfoMessage('Running Publish Cycle'); // remove or comment this line if you do not want to display to the user.
	new global.KnowledgeUIAction().publish(current);

})(current, previous);

 

View solution in original post

Hi @dadams3,

 

No worries at all and glad we could find a suitable resolution.

To help IT find articles, you can either steer them towards and leverage the existing module links under 'Knowledge' such as ALL opr Unpublished.

Alternatively you can create one or create a favourite so the department have a link to click to show the list of Article that are in the Draft state.

 

@dadams3- To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.


Thanks, Robbie

View solution in original post

3 REPLIES 3

Robbie
Kilo Patron
Kilo Patron

Hi @dadams3,

 

Whilst I understand the question and perhaps the request to avoid the extra step or click, can I ask to exercise a little caution here and check the why, and also perhaps add some boundaries around this, for example, restricting this to a certain Knowledge Base, or perhaps role, or other suitable criteria. This is exactly what logic is built into the 'Publish' button.

 

The reason why the Publish button is required is because there is a very low percentage of Articles that are written on initial creation which don't require a second read through or review from the author before sending for formal review and approval.

 

Taking on board what I've mentioned above, in order to answer your question directly, if you still want to go ahead (and you've factored in and restricted by Knowledge bqase etc), this can be achieved relatively easily by the introduction of a Business Rule that simply calls the same call to the workflow as the 'Publish' button - see below.

I still however want to advise caution and thought here and advise against it unless restricted.

 

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.


Thanks, Robbie

 

Screenshot 2024-07-26 at 17.32.13.pngScreenshot 2024-07-26 at 17.33.10.png

 

Business Rule Code:

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

	gs.addInfoMessage('Running Publish Cycle'); // remove or comment this line if you do not want to display to the user.
	new global.KnowledgeUIAction().publish(current);

})(current, previous);

 

dadams3
Tera Contributor

No problem and thank you for your take on this!

 

This change was requested for ease of use and avoiding an extra step as you stated Though, I do appreciate your point regarding the need to have a way of looking over the article before sending it off. We've ran into several cases where our IT team has hit submit and struggled to find the article they created (they are relatively new to the program).

 

Hopefully, this gives more insight!

Hi @dadams3,

 

No worries at all and glad we could find a suitable resolution.

To help IT find articles, you can either steer them towards and leverage the existing module links under 'Knowledge' such as ALL opr Unpublished.

Alternatively you can create one or create a favourite so the department have a link to click to show the list of Article that are in the Draft state.

 

@dadams3- To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.


Thanks, Robbie