Overview

The Confluence Product Requirements Blueprint can only have one workflow attached - the Requirements workflow.

Once a Space administrator attaches the workflow to this Blueprint

  • each time the page is edited it requires approval from one of the stakeholders
  • when all stakeholders have approved the content, the document automatically moves into a new state

For example, instead of manually updating the Document status field when content is updated on the Product Requirements Blueprint content, the workflow updates the field automatically.

On creating the content, the attached workflow will require you to define the users in the template page properties, Developers and QA

  • these users are referenced by the workflow using the value references @Developers@ and @QA@

These values will need to be defined for each page.

Attaching the Product Requirements workflow

In the space tools Templates dashboard

  • choose Attach workflow for the Product Requirements Blueprint

  • choose Attach in the dialog box to confirm


In the space tools Document Management dashboard the Requirements Blueprint workflow is added as an active space scope workflow.



When active all content created using the Product Requirements Blueprint will have this workflow applied.

Using the Product Requirements Blueprint

Once the Requirements Blueprint workflow is attached

  • choose the ellipsis menu to Create from template … 

  • select the Product Requirements Blueprint


  • choose Create

  • confirm the template by choosing Create


  • add the Developer and the QA page property values


  • after editing the content choose Publish

On the document, the Requirements Blueprint workflow is applied.

If you have not added the values for the Developer and QA page properties an on-screen message will be displayed.



Until you add values for both of these page properties, the Draft state transition will not be available.



Only when the page property values for Developer and QA are added, will a user will be able to transition to the first content review state.



The workflow accesses the page properties as the value references @Developer@ and @QA@. These values will be the users assigned to different content reviews in the workflow.

The workflow also updates the page property Document status value on each workflow state transition.



(info) Template variables cannot be accessed by directly by the workflow unless they are added as a page property value.

Atlassian