workflow macro

Added by Roberto Dominguez, last edited by Roberto Dominguez on Jun 05, 2008  (view change)
This macro is disabled-by-default, therefore if you want to use it, you have to enabled it first, as per the Approvals Workflow Configuration

Defines a workflow composed of {trigger} and {approval} macros.

Parameters Mandatory Default Description
spaces/space No current space A comma-separated list of space keys on which this workflow should be applied.
label No   The label associated with the workflow. Adding this label to a page will make the workflow active
stickylabels No   A comma-separated list of labels which, once added, they could be removed only by Confluence of Space administrators
adminusers No   A comma-separated lists of users which should be considered admin and could override any user restriction in approvals
css No   a URL to the CSS to be used. The CSS file can overriding existing CSS classes

Examples

{workflow:spaces=SITE, PAPERS}

The workflow will be active on the spaces SITE and PAPERS

{workflow:spaces=MANUALS|label=reviewable}

The workflow will be available to the space MANUAL and will be active in pages with the label reviewable

Labels

comalatech comalatech Delete
macro macro Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (6)

 

  1. Jan 23, 2008

    Simon Wheatley says:

    My experiments show that if you put two workflow definitions on the same page, o...

    My experiments show that if you put two workflow definitions on the same page, only the first one is respected; subsequent workflows are ignored.

    1. Feb 02, 2008

      Roberto Dominguez says:

      Yes, that is the case. Only one workflow per page is supported.

      Yes, that is the case. Only one workflow per page is supported.

      1. Feb 08, 2008

        Matt Bovett says:

        Is there any way to make it so a workflow is NOT active for pages with a particu...

        Is there any way to make it so a workflow is NOT active for pages with a particular label?

        There are several pages I don't want the approval process forced upon.

        I've got Comments appearing on all pages except pages that have the "no_comments" label. I figure all of these pages are pretty much the ones I don't want the review process to take place on.

        I tried this but it didn't work:

        {workflow:spaces=spacename|label=!no_comments}

        I've just been experimenting with this for a few hours so I'm still figuring out how it all works. Any tips would be appreciated.

        Matt

        1. Feb 08, 2008

          Roberto Dominguez says:

          Interesting scenario... What you can do now, is that by default a workflow is n...

          Interesting scenario...

          What you can do now, is that by default a workflow is not applied, but you can apply it if you add a label. What you want to do, is that by default a workflow is applied, buy you can exclude a page somehow.

          Not sure is this can be implemented they way you are proposing... left-side not-clauses can be complex...

          Here's another way of approaching it:

          • create a label workflow (i.e. reviewable label)
          • create another workflow for the entire space that will add the label reviewable whenever a page is created 
            {workflow}
    {trigger:pagecreated}
        {set-lable:reviewable}
    {trigger}
{workflow}
          • You can use the Label Management Plugin to add the labels to existing pages

          This way all the pages will get the workflow by default. When you remove the label, then there is no workflow.

          You could also restrict who can remove the reviewable label:

          {workflow}
    ...
    {trigger:labelremoved|lable=reviewable|usergroup=!moderator}
        {set-label:reviewable}
        {set-message:@user@}Only moderators can remove this lable{set-message}
    {trigger}
    ...
{workflow}

          1. Feb 10, 2008

            David Dembo says:

            I've already logged a feature request to allow NOT logic in workflow conditions ...

            I've already logged a feature request to allow NOT logic in workflow conditions - vote for it here.

            Also, I swear I added a feature request to implement {approve-page} and {reject-page} action macros, but can't find it anywhere in the list - the idea behind these macros would be to effectively allow pages to be auto-approved/rejected. E.g. you could apply the workflow to all pages, add a 'final' approval with a label=no_comments condition, and add a 'pageupdated' trigger with the label=no_comments condition that automatically gave that approval. I've just added a feature request here now.

          2. Feb 12, 2008

            Matt Bovett says:

            Thanks Roberto. I'm playing around with this now; I think it's going to do what ...

            Thanks Roberto. I'm playing around with this now; I think it's going to do what I need it to do. My server admin keeps disabling my plugins though (ThemeBuilder 3.0 beta, Approval Workflow, etc). I keep crashing the server with them and I guess they're seeing errors in logs caused by them.