Can a custom version number be used for existing documents in the Comala workflow?

[Franz]

Hi,

We have implemented a solution that starts with a fixed version number (“0”) when creating a Confluence page from a global workflow template.
Is it possible to use custom version numbers when the same approval workflow is applied to an existing Confluence page (=document)?
Are specific events triggered when the corresponding label is assigned?

Thank you in advance.

Best regards

[Tomislav Tobijas]

This sounds interesting @Franz 👀

For automating versioning, are you using the Comala feature or have you built a custom solution?

In any case, probably the team from Comala/Appfire could provide some additional insights on how to build something like that (based on previous experience). You could reach out to them through one of their support channels.

Cheers,
Tobi

[Franz]

Hi Tobi,

we use our own metadata:

{trigger:pagecreated}
{set-metadata:Dokumentenversion}0{set-metadata}
{trigger}
...
{trigger:pageapproved|approval=decide approval}
{increment-metadata:Dokumentenversion}
{trigger}

One possible solution might be to use the page version (directly from Confluence). I came across the following page:

https://appfire.atlassian.net/wiki/spaces/CDML/pages/649793463/How+can+I+display+both+the+current+draft+version+and+the+last+approved+version+on+my+page+for+my+users

Or prompt the user to enter another required parameter, as shown here:
https://appfire.atlassian.net/wiki/spaces/CDML/pages/649661052/Use+metadata+to+increment+composite+major+minor+patch+content+version+on+an+approval+decision+requiring+a+parameter

Cheers,

Franz