Workflow and Release Management


Workflow in connection to assignments is also further described here: Workflow and Assignments.

Workflow and Releases are part of the Version Management in Paligo. Both topics and publications are part of a workflow. The workflow in Paligo consists of 5 stages. Each stage is connected to the Release Management, which steps up the version number for each stage:

  • The first number is stepped up for a major release: 1.0.0

  • The second number is stepped up for a minor release: 1.1.0

  • The third number is stepped up for a review or translation stage: 1.1.1

You change the workflow stage in the Resource view for the item:

  1. Work in progress: For authoring and editing content. The initial stage of any document.

  2. In review: For SME review, proof-reading, etc. When the document is in Review, it is not locked, but marked as In Review.

  3. In translation: If you have multi-lingual content. While the document is in the Translation stage, the document is locked for editing.

  4. In translation review: For proof-reading or post-editing translations in the translation editor.

  5. Release: Final version of the document is released. When a document is released, it is locked for further editing.

Release Versions

Each time a release version is created (major or minor release), that version is saved and archived as a release "snapshot", an exact copy of the release all, its topic and other resources as they were at that point in time. It can be downloaded or restored in Paligo again.


If you need to start work on the next version, you do this by setting the publication to Work in progress again. The archived version will remain intact just as it was at that stage.

Procedure. Restoring and re-publishing a release

To restore and re-publish a release:

  1. Click the Restore button: restorebutton.png

  2. Select in which folder to restore the released version. 

  3. Make any changes you need, if any. Changes made to the topics in a restored release does not affect any of the topics in your current version in Paligo. It is a completely separate copy.

  4. Re-publish to any format you like.


Some important things to note:

  • Restoring releases is not something recommended on a regular basis, but only for exceptions when you need to re-publish an old version.

    If you need to keep multiple release versions in parallel in your system, with reuse between them, you should instead look into doing so with the help of reused topics and filters, possibly combined with branching.

  • Because the restored release may have had completely different variables and the like, such resources will be separate, and possibly partially duplicated. You may therefore want to clean such resources up after re-publishing your old version.

  • Archived releases (whether restored or not) use up your storage space. If you know that you do not need old versions, you should remove them.

Starting a New Version

When you have released a document, you can start a new version of it when the time comes for the next release. This is done by setting it to Work in progress.

Changing the status of a publication from Released to Work in progress only changes that publication component by default:


When you open a topic used in that publication, it will therefore still be released. You can of course release it directly on the workflow menu in the Resource View.

But you don't have to, when you open it, you get the option to change the status to start a new version right from the editor:


Should the publication (or other component where the topic is reused) not already be in Work in progress, Paligo will allow you to change the status of that publication too right there:


The topics that do not require change in this new version of the publication can (and will by default) remain in Released status: