Overview
When a Comalatech workflow is added to a page using Comala Document Management for Confluence Cloud you can use a workflow trigger event to action the publication of the page to the destination space.
If a publish trigger is added to the workflow, a workflow transition to the workflow final state (if present) will not publish the page.
Content in any state can also be published using the standalone publishing option.
Adding a trigger event to publish a page
If a user wants to publish using a different workflow event than "when reaching the workflow final state" the user can add a JSON markup for a trigger using workflow builder.
In the Quality Management Systems workflow, the following trigger markup would action publication of the content on a transition to the In Approval state instead of the transition to the final state (the Published state).
[
{
"event": "on-change-state",
"conditions":
[
{"state": "In Approval"}
],
"actions":
[
{"action": "publish-page"}
]
}
]
The trigger markup can be added using workflow builder.
Once the updated workflow with the trigger is added and applied the content will be published to the target destination space on each occurrence of the trigger event.
In our example, the page is published on the transition to the In Approval state.
The individual page is copied to the target destination space.
With the trigger publish action in the workflow, the transition to the workflow final state will not cause the content to be published.
Possible error when amending a workflow state name
If a workflow state name is changed using workflow builder or editing the JSON code markup the publishing trigger may not work in earlier versions of Comala Document Managemen for Confluence Cloud.
- the trigger will still be set to listen for the event linked to the previous state name.
Any change in the state name will need to be updated in the JSON code for the trigger.