You can use the same mechanism to set other properties, such as the document number, department and product, in a single table. You can add a property called ‘Version’ and update the value of this property for each new official release.Īdd this property to each of your controlled pages wherever you choose – typically right at the top of the page. It allows you to add your own properties to Confluence pages. Page Properties is a built-in feature of Confluence. Here are a couple of options for implementing official version numbering that you might like to consider: Option #1: Using Page Properties (Applicable for Cloud, Server and Data Center versions of Confluence) You will need to find a way to name and manage these official versions of a page. There’s no right or wrong approach, and the best method for you will be unique to your organisation. Or you could apply multilevel numbering similar to software releases: 1.1, 1.2 to 2.0, etc.You could stick with version number 1, 2, 3.I’ve seen several methods implemented in different organisations, ranging from simple to complex. How you register and maintain the official version of controlled documents is one of the essential decisions you should make before making the switch to Confluence. In between two official versions there are typically a few internal versions of a document, brought about by authoring and review iterations. In the case of controlled documents, a new version of the document usually means a new approved and finalised version. How does this apply to controlled documents? Let’s call this version saved with Confluence’s own versioning mechanism the ‘internal version’ of a document. Each previous version is still accessible, and it’s possible to compare any two historic versions.These will appear together with the history. Each time they save the document, users have the opportunity to add comments summarising the changes they’ve made.This provides details such as which users made each change and its modifications. The document history is easily accessible through the tools menu on every page.This innate versioning mechanism provides a host of features: This version is automatically tagged with a version number, starting at v.1, then progressing through v.2, v.3, etc. Each time you modify a document and save it, it adds a new version to the history. Versioning controlled documents with ConfluenceĬonfluence comes with built-in tools for versioning controlled documents. This is an updated version of the post: “Versioning controlled documents in Confluence” which proposes solutions both for Cloud, Server and Data Center Confluence instances.
0 kommentar(er)
