Workflow stages and actions

Overview

We use workflows to control the access to, verification and eventual approval of items. Only if an item is approved at all stages up to a published stage can it be viewed on the website.

A workflow must have at least one stage, but typically has more, and it always flows in a linear pattern. We can use a workflow to:

• review the accuracy of content.
• review content for any legal implications.
• review content to ensure it meets accessibility guidelines.
• ensure that no malicious code such as cross scripting attacks have been added to content.

A reject stage may be specified, which is a stags that is executed when a document is declined, before moving it to the first stage of the workflow. If the item is rejected at any stage, someone with editor access needs to correct or amend the item and resubmit it into the selected workflow (for approval). All items that are rejected (regardless of the stage they are at in the approval process) are sent back to the first (creation) stage of the workflow.

We can also specify that a comment must be entered on every move a document makes in the workflow or only on specific stages. This comment is added to the document's history section.

See

• Workflow stages
  
• Workflow actions
  
• Access Items during a workflow
  
• Joint approval
  
• Workflow example
  

Parent: Workflow and change management
Related:
Item status
Related:
Add workflow to managed pages