How to enable automatic inheritance of Confluence Space Workflows to its child pages?

[Vishnu Sivakumar]

When a child page, say A1 is created under the space A, the workflows which are existing in A should automatically inherited to A1. How can we do that?

Can someone help ?

[Einav Kivshany]

The workaround is applying to space and use labels to tell the service on which pages to run. Not very user friendly but it works.

[Sandy Johnson]

Hi Vishnu

I'm not sure what you are asking. We use Comala and our pages go through 3 states: Draft - initial state, Pending - approval requested and Operational - approved (or published) page.

Are you saying that if I create a new child page, you would want it to inherit what ever the state of the parent page currently has. For example, if the parent was Pending, you'd want the new child page to be Pending as well.

As far as I can tell, this is not possible. However, I'm not sure why you'd want to do that. The purpose of work flow is to ensure that all pages get the same treatment and go through the same rigor.

If this is not what you were referring, let me know.

Sandy

[Vishnu Sivakumar]

Hi Sandy,
Thanks for your response.

Please consider the below scenario.

A Confluence Space A have child pages A1, A2 and A3. If a Comala workflow CW1 is embedded in the Space A, The child pages of A should also embed the workflow CW1 with it's initial state. Also if a new child page A4 is created under A, A4 should also embed CW1 automatically. 

(Consider the workflow CW1 have 3 states - Draft , Pending and Approved. Each child of A should embed CW1 with the state "Draft" irrespective of the state of CW1 in A).

Can you please help me on this

Thanks & regards,
Vishnu

[Sandy Johnson]

Hi Vishnu

Sorry for the delay in responding.

I'm trying to understand the issue. Are you saying that all new pages should be assigned the Draft state when they are first added and this is not happening? Or are you saying that a new page should inherit the state of the parent page?

Sandy

[Einav Kivshany]

The original question was very clear. It's two years later and there is still no apparent way of applying a workflow to a page and have its child pages inherit it. No, not the same state, just the workflow template/logic.

Currently you can either assign a workflow to specific pages or an entire space which is pretty useless when your space includes a lot of content with different purpose.

The workaround is applying to space and use labels to tell the service on which pages to run. Not very user friendly but it works.

[Shannon S]

Vishnu,

Confluence doesn't have built-in workflows, so can you please let us know what you're referring to exactly? Are you using a specific add-on?

Kind Regards,
Shannon

[Vishnu Sivakumar]

Hi Shannon,

Thanks for the response.

I'm referring to the Comala Workflow add-on, which is  embedded to the Confluence Space.

Thanks & Regards,
Vishnu

[Shannon S]

Thanks Vishnu,

I added the appropriate tags so that it will get attention of the team behind the Workflows add-on so they can respond on this.

Thank you for your patience!

Kind Regards,
Shannon