Is it possible to unpublish a page (or revert a state) in Comala Workflows?

We use a global space workflow that is applied to all pages within a space. Increasingly we find that we have one or two pages in some spaces that we do not want to publish and we do not want the contents of the pages to be returned in the search results. Unfortunately, these "do no publish" pages frequently get published despite our efforts to the contrary. 

Is it possible to "unpublished" these pages? Or is it possible to somehow mark a page as exempt from the workflow that applies to rest of the space?

Resetting the state of the page back to draft doesn't help because the page still has a published version. I need a way to remove the published version or prevent the published version from ever being created for these specific pages. I'm happy to do this what needs to be done for the individual pages - there are only a few pages that need this special treatment out of the thousands that we expose to our customers.

Thanks in advance!


1 answer

Hi Teresa,

If you are using a version of Comala Workflows after 4.9, we have a feature where you can specify that pages with a particular label don't have the workflow enabled.  In other words, the workflow will still work on all the existing pages as it does now, unless the specific label is added to the page.  Adding the label on an existing page will de-activate the workflow.

Say this is the top line of your workflow markup:


and we don't want pages with the "noworkflow" label to get a workflow.  The top line of the workflow markup would then look like this:


You can also add "|stickylabels=noworkflow" to the above line, which means only admins can remove the label from the page.


That all said, de-activating the workflow on pages means that our draft/published functionality is disabled and all viewers of the space will be able to directly see the page content.  So to hide those pages we'll need to add a new global workflow to all the spaces to add page view restrictions at the same time the main workflow is deactivated.  Here's a sample workflow to do that:

{workflow:name=Hide Pages With No Workflow}

Replace "USERS" with a comma separated list of the users who can view/edit the page or alternatively use "group=GROUPS" with a comma separated list of the groups who can view/edit the page.  You can also use both the "user" and "group" parameter at the same time to add page restrictions for a combination of users and groups.


Please give that a try and let us know if you have any further questions.


Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 24, 2018 in Confluence

Atlassian Research opportunity with Confluence templates

Do you use templates with Confluence? Take part in a remote 1-hr workshop. You'll receive USD $100 for your time!   We're looking for people to participate in a   remote 1-hr workshop...

1,548 views 25 14
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you