Knowledge workflows
The publishing and retirement processes for a knowledge article are controlled by workflows defined for the knowledge base that the article belongs to.
You can assign different workflows to each Knowledge Base .
You can use one of the default workflows, or create your own workflows to define custom publishing and retirement processes for different types of knowledge.
For the workflows that require approval, you can configure which users can approve or reject by editing the getApprovers() function in the KBWorkflow script include.
Existing users of Knowledge Management upgrading to Zurich will have access to both workflows and flows in the Knowledge Base form. However, they will be able to use either workflows or flows for a knowledge base, with Workflow being the default option.
Cross selection between flow and workflow for publish and retire is not possible.
You cannot delete the approval records for knowledge flows. You can only approve or reject the records.
| Workflow | Description |
|---|---|
| Knowledge - Approval Publish | Requests 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. If ownership groups is not enabled, email notifications with a link to the article are sent to knowledge base managers for approval. A notification is also sent to authors or revisers of articles to inform them that their article has been approved or rejected. To turn on approval email notifications, set the glide.knowman.enable_approval_notification property to true. 注: Only the active user receives the notifications. |
| Knowledge - Approval Retire | Requests 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. If ownership groups is not enabled, email notifications with a link to the article are sent to knowledge base managers for approval. |
| Knowledge - Instant Publish | Immediately publishes a draft article without requiring an approval, or publishes on the scheduled publish date if set to publish later. |
| Knowledge - Instant Retire | Immediately retires a published article without requiring an approval. |
| Knowledge - Publish Knowledge | A subflow that moves the knowledge article to the published state. You can use this subflow when defining your own workflow. |
| Knowledge - Retire Knowledge | A subflow that moves the knowledge article to the retired state. You can use this subflow when defining your own workflow. |
- 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.
- An article and its translations have a parent-child relationship. Retiring a parent article does not automatically retire all its translated child articles.
Email notifications for approval workflows
- Notify approvers about knowledge articles submitted for their approvals.
- Notify authors about the approval status of their knowledge articles.