Comala Publishing - showing document approval data

[Katherine Lord]

When using Comala Document Management with Comala Publishing.

We approve in the collaboration space and then the workflow trigger the publishing to the target publioshed space.  In the target published space it does not show as approved anywhere and does not show the document approval macro of approver and date.  How is this information seen in the published space?

We do not want an auditor to be in the collaboration space hence need to see all the published metadata in the target space

[Elena Cantero]

Hi @Katherine Lord , @Anders Nymark Christensen ,

I’m the Product Manager for Comala Document Management and Comala Publishing for Confluence Cloud at Appfire.

I’d love to set up a call to walk you through how these apps work together and how to access approval information.

It would also be great to hear your feedback!

Feel free to book a time that works for you through my Calendly.

Looking forward to our conversation!

Best,
Elena

[Anders Nymark Christensen]

Dear Katherine,

Did you ever find a solutions to this?

We are in the same situation, and had planned on using approval macros to show who approved and when. However, they are also overwritten when publishing to the target space.

[Matteo Gubellini _SoftComply_]

Hello @Katherine Lord ,

We have a Change History Table App for Comala Document Management that reports the approvals inside the page and also works in published pages, see https://marketplace.atlassian.com/apps/1228268/softcomply-change-history?hosting=cloud&tab=overview

if interested

Matteo

[Kristian Klima]

Hi @Katherine Lord 

I'm running Document Approval with Publishing, the setup is otherwise identical to yours.

Approval apps are designed to control workflows in one single space. In combination with Publishing, my understanding is the idea is that whatever is in the Target space is considered Approved.

Which is the case, isn't it, setting a document to Approved triggers Publishing which pushes the Approved page to the target space.

The lifecycle docs management takes place in the source space - both the Approval and the Publishing app give us the tooling to see which pages are in which stage (approved / not approved, synced / out of sync).

As for the date of 'approval' in the target space, the synced date and the last updated date are identical.

It seems that you can set up the Approval app in the target space but that would, in my opinion, defy the purpose of the Approval > Publishing setup.