Document saving

Saving changes to a document uses a change commit model. While changes are auto staged to the document, changes are not saved to the immutable document record until the changes have been committed.

Staging

Before you commit changes to a document, the changes are staged in a buffer. This buffer is saved to the server and common to every user working on the document at the same time.

The contents of the stage may be reverted by a user and is not part of the immutable record of the document until the changes have been committed.

Committing

Committing staged changes to a document saves them to the immutable history of a document branch. Staged changes to a document can be committed by pressing the Commit button on the Home tab of the document editor toolbar. A dialogue will be shown with a list of changes being committed. You can optionally enter a commit message summarising the changes made.

Staged changes can be unstaged from a commit by pressing the revert change icon next to the change.

When you are ready to commit the staged changes, press the Push commit button.

Reverting a change that is referenced by another staged change will cause the server to reject the commit.

Reverting

Staged changes to a document can be reverted by pressing the Revert button on the Home tab of the document editor toolbar. You will be prompted asking if you are sure you want to revert the changes. Once these changes have been reverted they cannot be recovered.

Forking

A copy of a document can be made by using the Fork functionality. The history of forked documents is preserved and linked to the source document. A document serving as a template can be forked to create a new document with that template.