|Number of votes:||11|
This feature was released as a Beta feature in CMS 10.1.0 and is still under development.
You can read more about how you enable Beta features in Fredrik Tjärnbergs blog post.
Content approvals is a way to make sure that content is reviewed and approved before it is published. It works as a new state (In review) between Draft and Published, which is visible in the Versions gadget. When an editor has finished working on a content item, the editor cannot publish it but has to set it as Ready for Review. One or more appointed reviewers must then approve the content item before it can be published. The reviewers are defined by an administrator in an Approval Sequence.
Content approvals do not apply to blocks at this stage.
The Approval Sequence is set up by an administrator and can have any number of approval steps and any number of approvers in each step. If the page has multiple languages there has to be at least one approver for each language in each step.
The approval sequence overview is opened from the context menu in the page tree:
As a part of this release, we made the context menu pluggable. So now you can easily add items to the context menu.
Content Approvals work with Projects but only on a per-content basis, and not for the whole Project.
The approvals can be driven through the Core API, but beware that it's also in Beta and will change a lot as we're continuing on Content Approval. Do take a look at the IApprovalEngine and IApprovalEngineEvents in the meantime. Use it to react to content moving through the sequence, or automatically reject or approve changes.
You can read more about Content Approvals in the User guide documentation.
There are more things coming with Content Approvals, but please let us know what you like or if there's anything you want us to focus on.