Overview
Use the {approval}
macro to add content-focussed reviews to workflow states.
Content has to be approved before it can progress to the next state, or it can be rejected to send it back for more edits. Once all reviewers agree – either on Approve or Reject – the workflow will transition to the state defined by the approved
or rejected
parameter on the parent {state}
macro.
Where to use it?
Optional.
One or more {approval}
macros can be put in a {state}
macro.
Within a {state}
, each {approval}
must be uniquely named. Can not be used if the {state}
has a {state-selection}
macro.
Parameters
Parameter | Required | Default | Notes | Ver |
---|---|---|---|---|
unnamed first parameter | Name of the content review.
| |||
description | The description for the approvals:
| 5.7+ | ||
Conditions | Optionally define additional requirements which must be met prior to content approval – see: Conditions. If one or more conditions are not met, the Approve/Reject buttons will be disabled. However, reviewer assignment will still be possible.
| |||
Reviewers / AssigneesSpecify if, who and how reviewers are assigned to the content review. † Parameters ‡ Prefixing the list with If there are 15 or fewer possible assignees (as specified by the | ||||
assignable | false | Can the user assign reviewers?
Note: Assignees must have permission to edit the content and also be member of
| 3.2+ | |
credentials | 0 | To what extent do reviewers need to confirm their identity when reviewing?
The requirements stack, so a value of
| ||
exclude | List users who are not allowed to review.
Note: While excluded users are not able to be assigned or Approve/Reject, they can still assign other users as reviewers where applicable (eg. if the
| 4.16+ | ||
group † | Reviewers must be a member of the specified user group(s):
Note: Users who do not have Edit content permission will not be allowed to review.
| |||
minimum | 0
| Define the minimum number of reviewers required for the content review to be approved.
| ||
selectedapprover or selectedapprovers parameters, the minimum defaults to 1 . | ||||
| false | Remember the assignees for reviews with this name?
| 4.14+ | |
roles | false | Enable approval roles feature
| 6.4+ | |
selectedapprover † | A single reviewer must be assigned from the list:
Note: Users who do not have Edit content permission will not be allowed to review.
| |||
| One or more reviewers must be assigned from the list:
Note: Users who do not have Edit content permission will not be allowed to review.
| |||
| Reviewers must be in the specified list:
Note: Users who do not have Edit content permission will not be allowed to review.
| |||
allowedassignusers | Assigners must be in the specified list:
Note: Users who do not have Edit content permission will not be allowed to assign. It can be used along with the
| |||
allowedassigngroups | Assigners must be a member of the specified user group(s):
Note: Users who do not have Edit content permission will not be allowed to assign. It can be used along with the
| |||
User InterfaceThese parameters are used to customise the user interface of the Workflow Popup. | ||||
approvelabel | Approve | Set the caption of the Approve button.
| 5.1+ | |
rejectlabel | Reject | Set the caption of the Reject button.
| 5.1+ | |
|
| When using multiple
| ||
Deprecated ParametersThe following parameters should no longer be used. | ||||
final | OBSOLETE Use the | |||
label | DEPRECATED Use the Require that the page or blog has the specified label before a review can be made. |
App configuration
Setting | Where | Notes |
---|---|---|
Approval – Assignee | While enabled, assignees will receive email notifications about events during the content review. | |
Approval Comment | While enabled, reviewers will be forced to comment when they Approve or Reject during content reviews. | |
Page Update Reset Approval | While enabled, if the content is edited whilst it is under active review then any approvals made during that active review will be reset. | |
Workflow Activity and Drafts Visibility | Who can see and interact with the Workflow Popup |
Example
{workflow:name=Example} {state:Editing|submit=Review|colour=#ffab00} {state} {state:Review|approved=Published|rejected=Editing} {approval:Review this page|assignable=true|roles=true} {state} {state:Published|final=true|updated=Editing} {state} {workflow}
If roles=true, a user can be assigned a reviewer role. This can be created when adding the assignee or chosen from any previous role created.
Events
Content reviews generate the following Events
approvalunassigned
newsapproved
newsapprovalassigned
newsrejected
pageapproved
pageapprovalassigned
pagerejected
Related macros
The following macros are related to Reviews
{approve-page}
{approve-children}
{reject-page}
{reject-children}
{state}
–approved
andrejected
parameters
All examples
-
Adding Multiple Reviews — Add multiple reviews to a content review, set assignee requirements and review dependencies, list ordering
-
-
-
Assignment Examples — Define who can take part in, or be assigned to, a content review.
-
Blog Post Events — Workflow events associated with blog posts
-
-
Customise Approval Buttons — How to change captions of the Approve and Reject buttons created by the
{approval}
macro. -
Fast-tracked Rejections — How to require everyone to Approve, but only need one person to Reject
-
-
Make tasks disable a review — Use a Value Reference Condition to check that all tasks are complete. You need the Reporting for Confluence app in addition to Comala Workflows.
-
Reviewer Authentication — This example shows how to authenticate reviewers during a content review.
-
State expiry dates — Using state expiry dates, defining them with metadata, and making them editable
-
Transitions — Transitions create the routes between states