Display page version from draft space to published space

[Ally Lancaster]

Hey Community!

I am using a user macro to display the confluence version number which is working great.

## @noparams
Issue #$content.version

But I would also like to display the version number of the same page from a difference space. I am using Comala publishing to publish from a draft space to an approved space.

In the draft space I would like to display the approved version page number followed by the draft version page number.

In the draft space it would look like this:

• Version: 4.11 OR;
• Approved version: 4 | Draft revision: 11

In the approved space it would look like this:

• Version: 4

Is this possible? Thank you :)

[Goriana Ivanova]

Hi Ally,

You can do that by using Comala Workflows and Comala Publishing.

In the draft space, you need to save the approved version using set-metadata macro where "@version@" is a value reference to the content version.

   {trigger:pageapproved|approval=ApprovalName}

        {set-metadata:approvedversion}@version@{set-metadata}

        {publish-page}   

    {trigger}

You can display the draft version and the approved version in pageheader macro using get-metadata macro:

   {pageheader:visibility=all}

               Approved version:{get-metadata:approvedversion}| Draft revision:{get-metadata:version}

    {pageheader}

To copy the draft approvedversion metadata to the published space, you need to check "Page Properties" checkbox in Publishing Options screen in Space Tools/Publishing Configuration.

Lastly, to show pageheader in the Published space, you need to add the following workflow:

{workflow:name=Published Space Header|hideStates=true}

    {description}

        This is the workflow for the published space to show metadata from the draft space

    {description}

    {state:invisible|final=true}

    {state}

    {pageheader:visibility=all}

        Version: {get-metadata:approvedversion}
       

        {pageactivity}

Hope this helps.

Cheers,

Goriana

[Meera_Amanullah]

Hi @ @Goriana Ivanova,

I'm in a similar situation to this question.

We are using a Confluence space for editing and publishing it to Scroll Viewport.

I am using the get metadata macro and fetching the current version, which is good for the Confluence space view while writing the content.

But I need the approved version number alone in the viewport for end-user reference.

Example:

In the Confluence space (Editor view) - Version 1.10

On the Viewport (End-user view) - Version 1 (last approved).

Could you please help me with this?

The code im using is as follows:

{trigger:pagecreated}
{set-metadata:currentversion}0.0{set-metadata}
{trigger}
{trigger:pageupdated}
{increment-metadata:currentversion|increment=0.1}
{trigger}
{trigger:pageapproved|approval=Review}
{increment-metadata:currentversion|increment=1.0}

And on the page I'm using the get-metadata macro and property as the current version.

Thank you

[Kris Klima _K15t_]

Hi @Meera_Amanullah 

Last versions are not the only thing you need. You also need to 'convert' links for your Viewport space.

Otherwise links between pages in your source space will move to the target (Viewport space). As a result, links in your Viewport site will lead to Confluence.

Facing the same problem as you in my previous company, I used Comala Document Approval and Comala Publishing.

In your Source space, you approve a page and it will be synced to your Target space. You will built your Viewport site from the Target space.

Comala publishing also takes care of links.

You can also look into Space Sync for Confluence (Ricksoft) and Workflows for Confluence (Appfox).

Another option is to use Scroll Documents which can also publish content from one space to another.

If you have more questions, feel free to ask.

Disclaimer: I work for K15t now, maker of Scroll Sites (formerly known as Viewport) and Scroll Documents.

[Meera_Amanullah]

Hi  @Kris Klima _K15t_,

Thanks for the response.

I am using the Comala Document Management, Scroll Viewport, and Scroll Documents for pdf generation. My first priority was to get this version number automated; I will get in touch with you on the other issues like converting links soon.

Thank you.

[Kris Klima _K15t_]

@Meera_Amanullah 

When you do, please, start a new question as this thread started 7 years ago.

That way, whatever we discuss is likely to help more users on the Community.

Thanks.