Aurora: 3-step workflow for Knowledge base articles and blog posts
Let’s walk through an example of how a blog post moves through the three-step workflow until it is published. The same applies to Knowledge Base articles.
Before you continue, you may find it helpful to first read the articles on assigning authoring and publishing roles to members and what these roles help with.
- The BlogAuthor clicks Create a blog post to start a new blog post.
- The BlogAuthor writes the blog post. They can either click Save Draft to update the blog post later or Submit for Review to send the blog post for review to the BlogEditor. Assume that they click Submit for Review.
The draft is saved. The version number of this draft is 0.1. The status appears on the top-right corner. In this example, the draft status is Awaiting Review. The Version History displays this version as v0.1. The Version History also lists all the actions taken on this blog post until it is published in the community blog.The blog post is now in the Awaiting Review state and waiting on the BlogEditor to take action.
Note: BlogAuthors and KBAuthors can still recall blog posts and articles at this point in the workflow.
- The BlogEditor opens the Manage Content dashboard and sees that there are articles in the Awaiting Review state.
- The BlogEditor can open the draft to review or edit by either:
- clicking Edit Draft on the draft page:
OR
-
clicking Edit from the Manage Content dashboard
The BlogEditor can:
- Edit to make changes.
- Return to Author if the blog requires changes from the BlogAuthor.
- Submit for Publication to send the article to the BlogPublisher.
- clicking Edit Draft on the draft page:
- In this example, the BlogEditor clicks Submit for Publication. The draft moves to the Awaiting Publication state and is forwarded to the BlogPublisher.
- The BlogPublisher opens the Manage Content dashboard and sees that there are articles in the Awaiting Publication state.
- The BlogPublisher can either click the name of the blog post to review the draft or take actions from the Manage Content dashboard.
The BlogPublisher can:
-
- Return for Review to send the blog post back to the BlogEditor.
- Publish to publish the blog post in the community blog.
- Schedule for Publication to publish the blog post at a later time.
In this example, the BlogPublisher clicks Publish.
-
The article is published in the Community with version number 1.0.
You can view the history of the blog post even after it is published
Learn more about restoring older versions of a published blog post or knowledge base article.
Learn more about editing published blog posts or knowledge base articles.
Workflow process for members with multiple roles and permissions
You can assign more than one of the default roles to a member.
The drafts have to go through the review state to be published.The below screenshot shows the workflow page where the member has all the three default roles. The Submit for Publication button will not be visible until the draft passes the review state.
But if the member has all 3 default roles, and the draft has passed the review state, then the member can take all the workflow actions.
Related topics: