This site has moved to the integrated Appfire documentation and information site for our apps.

From February 2024 this site is no longer updated.

Take a look here! If you have any questions please email support@appfire.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

USE CASE

Comala Publishing space-to-space publishing provides a centralized space for final versions of documents to reside. At the same time, permission-based access and up-to-date messaging support internal processes needed to meet regulatory requirements and standards, for example, ISO or SOC2.

What are the ways teams benefit?

Mitigate non-compliance risk by maintaining accurate and current information that complies with required laws and regulations, avoiding fines, penalties, and legal actions.

Reduce the risk of data breaches and protect sensitive information by restricting access to authorized users and groups.

Prevent errors and compliance violations resulting from outdated information. Quickly sync to the published space so authorized users have access to the latest version of a document.

Different space publishing with Comala Document Management

Comala Document Management automates the document lifecycle and approve pages to a final state in the Comala Document Management workflow. The final state page can be automatically published and synced to a different space using Comala Publishing.

Different-space publishing allows you

  • to edit draft pages in one space in a cloud site

  • then publish these pages to another space (in the same cloud site)

The Comala Publishing for Cloud app must be installed to enable different-space publishing.

/wiki/spaces/CPCD/pages/7468224603 can only be used to publish Confluence Cloud pages. Comala Publishing cannot publish bog posts.

To get started

You can undertake an initial publish and sync of your all the pages in your source space using the space publishing option.

Comala Publishing is designed to publish content from a source space to a target space that is empty!

Your target space will be your public space for your pages. Access to your published page content in this space can be easily managed by the space permissions.

Publishing the approved pages using Comala Publishing

In the instance you need to have

You must have

  • added a target space for the published content in the space settings of the draft space

  • an active Comala workflow on the content and the workflow must include a final state

  • view and edit permission for both the draft space and the target space for publishing

Publishing a page occurs on a transition of the workflow on the page to the workflow final state.

Only one state in a workflow can be set as the workflow final state.

In the example below the final state in this workflow is the Approved state.

The content in the draft space transitions to the final state of the applied workflow.

Additional on-screen messages confirm the publication of the current content to the target space defined in the space settings Publishing dashboard.

Navigate to the target space to view the published content and the location in the hierarchy.

If the page is the first to be published in the target space, it is copied to the root of the target space.

An on-screen message in the draft space will warn the user that the current page has been copied to the root of the target space. The target space is identified by the space key in the message.

Where possible the publishing of content to the target space will maintain the hierarchy of the draft space.

Comala Publishing Cloud only publishes pages but cannot publish blog posts.

Although the space home page cannot be published, the home page in each linked space can simply include Confluence page macros (children; page tree) to display the pages in that space.

Compliance

Comala Publishing together with Comala Document Management includes features that enable you to enforce compliance with industry standards and regulations.

  • Comala Publishing use can be integrated with Comala Document Management to deliver approved and up-to-date content to designated, centralized locations for permitted audiences. As a result, collaboration can continue while preserving published versions.

  • /wiki/spaces/CDMCD/pages/13949468673 can create /wiki/spaces/CDMCD/pages/6969366578 and audit trails that provide evidence of document approval and compliance. You can also set up automatic archiving and retention policies that ensure documents are stored and disposed of in accordance with regulatory requirements.

In addition to taking advantage of technical elements, compliant systems must also implement the necessary procedural and administrative controls.

Information on how Comala Document Management and Comala Publishing can assist you with Part 11 compliance, is available in our compliance statement for FDA Title 21 CFR Part 11.

This compliance statement was originally designed for our Confluence server and data center apps. However, many of the elements for 21 CFR Part 11 translates to Confluence Cloud with Comala Document Management solution (e-signatures).

In regard to the Atlassian Confluence Cloud environment, you will need to have a controlled environment and a working environment to help satisfy 21 CFR Part 11. To help meet this we recommend the use of our Comala Publishing app together with the /wiki/spaces/CDMCD/pages/13949468673 app.

Once pages in a space have gone through the review and approval process provided by the Comala Document Management workflow, the Comala Publishing app can be used to automatically publish and sync the approved content to another target space for your published pages. In this published space, users will have view-only rights to the published pages.

Customer case studies

We have a number of our customers who use Comala Publishing and Comala Document Management as part of their review and approval document and compliance process including helping to attain FDA Title 21 CFR Part 11 in the life sciences industry.

 

Disclaimer

Appfire does not claim compliance or certification of any of our tools. In addition to taking advantage of technical elements, compliant systems must also implement the necessary procedural and administrative controls.

The Appfire Trust Centre has the latest information on the security, privacy, and compliance of our uniquely positioned products and services.

  • No labels