Setting workflow state in cloud
Background
The current workflow state is migrated to cloud - but not the full workflow history.
The workflow applied in cloud must have the same workflow state names as the server workflow. Otherwise, the current workflow state is not migrated.
Setting the workflow state in cloud
If a different state is required to the migrated state, the workflow state for all pages for an applied space workflow is set using Initialize states in the space settings document management dashboard.
For the active workflow
choose Initialize States icon
In the Initialize States dialog box
select a State from the dropdown many
check the Override preexistent states checkbox option
choose Initialize button
If setting the same state for all pages in the space is not an option, an administrator can use the debug console on a page.
This is a dark feature that can be temporarily enabled by accessing the dark features section of your Confluence instance.
enable the Debug Tools as a dark feature by adding the following URL in your browser
<HOST>/wiki/admin/darkfeatures.action
scroll down to Enable dark feature
add
cwc.debug
choose Submit
Navigate to each page
open the workflow popup on a page
select the ellipsis menu
choose Debug tools
choose the Transition to … dropdown menu
select the required workflow state
Wait for the console Loading… message to disappear and the updated display of JSON code in the console Content Property window.
The new current state is displayed, as below, in the Content Property window in the console.
{
"enabled": true,
"name": {
"value": "Approved"
}
This new current state is also displayed in the Status window in the console.
choose Close
The new state name is added as the workflow status byline on the page.
A record of the workflow history for audit purposes can be added as a CSV file attachment to a page before migration using the Attach Activity option in server.
Related pages