Names the workflow. Workflow names must be unique within a space.
A comma delimited list of labels. The workflow will apply only to pages that have one of the specified labels (or none of the labels if the
|No||false||Boolean value to reverse the label parameter.|
Comma-separated list of types of content the workflow applies to. If omitted the workflow applies to all supported types. Supported types are presently
A comma-separated list of labels which, once added, can only be removed by a Confluence or space administrator.
A comma-separated lists of users who should be considered workflow administrators. Using this parameter expands the access to the admin=true function beyond Confluence and space administrators.
The template name to be rendered as a header on all pages on which the workflow is present. The template reference can include the space, i.e.,
The template name to be rendered as a footer on all pages on which the workflow is present. The template reference can include the space, i.e.,
|No||Boolean value to turn the progress tracker on or off for this workflow.|
|No||Boolean value to update status macros in the page with the current workflow state when the state is changed. Useful when working with predefined templates that already include the status macro. See the pagestatus macro for another way to display the workflow state within a page.|
You can create a template and have that template rendered on all pages on which the workflow is active. For example, create a template
PageHeader in the space
DOCS with the following Confluence wiki markup code.
The workflow refers to the
For more information of the wiki markup language, see Confluence Wiki Markup. The use of the
footertemplate parameters is an alternative to defining the header and footer in the workflow code with the pageheader and pagefooter macros.
If the reference to the template does not specify a space key, it will refer to a page in the same space where the workflow is active.