Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
{repository-workflow:
Wiki Markup
Excerpt
hiddentrue
namerefinedpageimage
Image Added
Info

Importing workflows

Find out how to Import Workflows

Editor and staff approval workflow

requires v3.1.9+

com.comalatech.

...

workflow.

...

repository.

...

categories

...

.label:General|Bundled

-Image Added

  • Staff edit a page

  • When the page is ready, the content is submitted for approval in the Ready state by a user defined using Reviewers

  • Content is not published until the Editor-in-Chief

...

  • gives

...

  • approval in a second approval state, Reviewed

  • Reviewers and Editor-in-Chief are workflow parameters (value references). Their values are defined in the space admin workflow configuration



Editor and staff approval workflow Markup
Code Block
{workflow:name=Editor and staff approval workflow|key=com.comalatech.sample.approvals.02}
    {description}
        AThe ContentPublishing Review Workflow thathas marksfour astates.
pageReady: asEdited 'Active' for now and that will automatically transition 'For Review' after a defined period of time.  Once expired to 'For Review', authors can change again to 'Active' or to 'Obsolete', or to 'Requires Approval' to be approved or rejected.
    by Staff. Reviewed: Reviewed by Managers. Published: Approved by Editor-in-Chief & viewable publicly.
You can define the Reviewer and Editor-in-Chief in the Space Admin Workflow Configuration. 
    {description}
    {workflowparameter:Expiration periodReviewers|description=After this period pages will expireReviewers group|type=durationgroup}
        P7Dconfluence-users
    {workflowparameter}
    {state:Active|expired=For Review|taskable=true|duedate=@Expiration period@}workflowparameter:Editor in Chief|description=User able to give final approval|type=user}
       @user@
    {stateworkflowparameter}
    {state:For ReviewDraft|taskablesubmit=trueReady}
    {state}
    {state:Requires ApprovalReady|approved=ActiveReviewed|rejected=ObsoleteDraft}
        {approval:ApproveReview|group=@Reviewers@|assignable=true|user=<at:var at:name="assigner" />,<at:var at:name="assignee" />}
    {state}
    {state:Obsolete|hidefrompath=trueReviewed|approved=Published|rejected=Ready}
    {state}
    {trigger:statechanged|state=Active}
 approval:Editor in Chief|final=true|user=@Editor in Chief@}
      {remove-label:for-review}
  {state}
     {remove-label:obsoletestate:Published|final=true|rejected=Reviewed|updated=Ready|hideselection=true}
    {triggerstate}
    {trigger:statechangedpageapproved|stateapproval=For Review}
        {setsend-label:for-review}
        {remove-label:obsolete}email:user=@Editor in Chief@|subject=Page ready for final approval}
     {trigger}   The  {trigger:statechanged|state=Obsolete}
        {remove-label:for-review}
  page @pagetitle@ has been approved by @user@ and is waiting for your final approval.
     {set-label:obsolete}
    {trigger}
    {trigger:statechanged|state=Requires Approval{pageactivity}
        {set-metadata:assigner}<at:var at:name="user" />{set-metadatasend-email}
    {trigger}
{workflow}

    {workflow-body}
{repository-workflow}

...

This workflow includes workflow parameters. When applying a space workflow

  • a parameter reference value may only be available for use by the workflow after a workflow process, such as a transition, occurs. For example, the initial state should not include the use of the parameter reference value for a due date or pre-assigned reviewers for approvals to avoid blocking your workflow. Alternatively, you can choose to Initialize states when applying a space workflow

  • the parameter value is retrieved from the space parameters dashboard on first application of a workflow to a page or blog post. This value may be different to the value used in the workflow template