{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":47719,"path":"servicenow-platform/knowledge-management/r_KnowledgeFlow.md","title":"Knowledge Flow","bundle":null,"doc_type":null,"release":"australia","body":"\n# Knowledge Flow\n\nThe publishing and retirement processes for a knowledge article are controlled by flows defined for the Knowledge Base that the article belongs to.\n\nYou can assign different Flow processes to each Knowledge Base.\n\nYou can use one of the default flows, or create your own to define custom publishing and retirement processes for different types of knowledge.\n\nFor flows that require approval, you can configure which users can approve or reject by editing the getApprovers\\(\\) function in the KBWorkflow script include.\n\n<table id=\"table_eqc_lfl_1r\"><thead><tr><th>\n\nFlow\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nKnowledge - Approval Publish\n\n</td><td>\n\nRequests approval from a manager of the knowledge base. Articles in approval are In Review state before moving to Published state once approved or to Scheduled for publish if set to publish later. If the manager rejects the request, the workflow is canceled and the article remains in Draft state. If ownership groups is enabled, email notifications with a link to the article are sent to the ownership group members for approval.\n\n If ownership groups is not enabled, email notifications with a link to the article are sent to knowledge base managers for approval.\n\n A notification is also sent to authors or revisers of articles to inform them that their article has been approved or rejected.\n\n To turn on approval email notifications, set the **glide.knowman.enable\\_approval\\_notification** property to `true`.\n\n **Note:** Only the active user receives the notifications.\n\n</td></tr><tr><td>\n\nKnowledge - Approval Retire\n\n</td><td>\n\nRequests approval from a manager of the knowledge base before moving the article to the retired state. The workflow is canceled and the article remains in the published state if any manager rejects the request.If ownership groups is enabled, email notifications with a link to the article are sent to the ownership group members for approval.\n\n If ownership groups is not enabled, email notifications with a link to the article are sent to knowledge base managers for approval.\n\n</td></tr><tr><td>\n\nKnowledge - Instant Publish\n\n</td><td>\n\nImmediately publishes a draft article without requiring an approval, or publishes on the scheduled publish date if set to publish later.\n\n</td></tr><tr><td>\n\nKnowledge - Instant Retire\n\n</td><td>\n\nImmediately retires a published article without requiring an approval.\n\n</td></tr><tr><td>\n\nKnowledge - Publish Knowledge\n\n</td><td>\n\nAction that can be used to publish the knowledge article.\n\n</td></tr><tr><td>\n\nKnowledge - Retire Knowledge\n\n</td><td>\n\nAction that can be used to retire the knowledge article.\n\n</td></tr></tbody>\n</table>**Note:**\n\n-   Only administrators and knowledge administrators can view the retired knowledge articles. To reuse a retired article, administrators and knowledge administrators can republish the article. For more information, see [Republish a retired article](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/knowledge-management/republish-retired-article.md).\n-   An article and its translations have a parent-child relationship. Retiring a parent article does not automatically retire all its translated child articles.\n\n"}}