Workflow final state version

Overview

With a workflow, each document (page or blog post) can have concurrent draft and approved versions.

A single state in your workflow must be set as a final state.

Workflow with a final state

A workflow with a final state helps differentiate to your users between content in a draft state and content in the final state ((approved content)

In the Basic Approval Workflow, the final state is the Approved state.

The other states in the workflow are considered as draft content.

If the page has been previously approved (transitioned to the final state), the workflow byline includes a link to view the latest approved version. This version was created on the last transition to the final state.

Adding a final state to a workflow in Cloud does not change any user access to a page or blogpost.

In Confluence Cloud, user permissions to the page are managed by using the page level permissions.

The workflow final state can be used by the app in a number of ways

Using Comala Document Management for Cloud together with Comala Publishing, the final state transition is the default event to publish a page to a different space.

Workflow final state and published version

final state will be, by default, displayed on the page subtitle with a green state indicator circle (or green lozenge in workflow builder visual editor)

The transition to the final state sets the workflow final state version. When the content is in any other state in the workflow the content is draft content.

The View approved breadcrumb link to the Confluence version created on transition to this final state is displayed on the page sub-title when the page or blog post is transitioned to another state in the workflow.

The transition to a final state can also be used to publish a page to another space using the Comala Publishing app