Versioning, also known as revision control, is the management of changes to documents and other information stored in a file system or repository. The main goal of versioning is to prevent information from being overwritten or deleted during everyday work with documents. Changes are kept track of, and a mechanism is offered to restore a particular document to a previous version.

The versioning system of sensenet also provides mechanisms for keeping the published version of a document under heavy editing visible to outside users, while you continue to work on the latest, draft version.

Enable versioning

In sensenet, versioning is disabled by default. It can be enabled for folders or content lists, or even for individual contents by setting the value of the Versioning Mode field. (Sub-folders inherit versioning settings by default.)

Versioning mode can be set as the followings:

None0The default setting of the Root folder, no versioning.
Inherited1The folder inherits its versioning mode from its parent. This is the default setting for all other content.
Major only2Only major versions (1.0, 2.0,...) are preserved.
Major and minor3Every version is preserved (1.0, 1.1, 1.2,...).

With the following example you switch on versioning for a workspace:

url: "/OData.svc/Root/Content('IT')",
type: 'PATCH',
data: {
  "InheritableVersioningMode": ["3"],

Content states

Content in the repository can have several non-numeric version states:

AAPPROVEDOnly a major version can be in approved state: 1.0A or 2.0A. The last approved version of the content is that users with low level permission can see.
LLOCKEDWhen a content is locked, only the user who locked it can modify it.
DDRAFTA draft version is only visible to users who have permission to see minor versions of a content. Any other user will see the last public version.
PPENDINGWhen approval is enabled in a folder or list, then contents cannot be published without approval.
RREJECTEDIf a content is not correct, the user with approving rights can reject it. This means it is not published and should be refined.

Get current version of a content

Current version is always saved as a value of the field Version on every content. As you can see in the following code snippet you can get the current version number as any of the common field values:

url: "/OData.svc/Root/Content/IT/Document_Library/Calgary('BusinessPlan.docx')?$select=Version",
type: 'GET'

Get a specific version of a content

You can easily get a specific (older) version of a content knowing the actual version number. You can set it as a param of the OData url like in the next example:

url: "/OData.svc/Root/Content/IT/Document_Library/Calgary('BusinessPlan.docx')?version='V1.0.A'",
type: 'GET'

Checkout a content for edit

Following example shows you how to checkout (lock) a document:

url: "/OData.svc/Root/Content/IT/Document_Library/Calgary('BusinessPlan.docx')/CheckOut",
type: 'POST'

Check-in a content

With the next example you will check-in a document adding a comment:

url: "/OData.svc/Root/Content/IT/Document_Library/Calgary('BusinessPlan.docx')/CheckIn",
type: 'POST',
data: "models=[" + JSON.stringify({
    checkInComments: 'Adding new contract',
  }) + "]"

How to know if a content is locked

If a content is checked out by someone it became locked for other users. Locked is also a field on every content so you can easily check if a content is locked or not. With the following code snippet you can find out if a content is locked and by whom it is locked:

url: "/OData.svc/Root/Content/IT/Document_Library/Calgary('BusinessPlan.docx')?$select=CheckedOutTo/Name&$expand=CheckedOutTo",
type: 'GET'

Save a draft version

When versioning mode is set to 'Major and minor', you are able to work with draft versions. If you want to create a draft, save to content without publishing the changes (e.g. using the Publish action). You can save the content over and over again, until you use the publication, only draft versions are generated.

Publish a new major version

As it is mentioned before using the Publish action makes a content public, creating its major version. In the next example you can see how to publish a document:

url: "/OData.svc/Root/Content/IT/Document_Library/Calgary('BusinessPlan.docx')/Publish",
type: 'POST',

Undo changes

It can happen that you don't want publish your changes and you want to withdraw them. Using the next example you will be able to undo the changes that you've made on a content:

url: "/OData.svc/Root/Content/IT/Document_Library/Calgary('BusinessPlan.docx')/UndoCheckOut",
type: 'POST'

Force undo changes

It is also possible to undo other users' changes on a document. This feature is really useful when somebody leave a content in checked out (locked) and does not able or willing to finish the work on the content. If you are allowed to do that (it can be set with permissions) with the next snippet you can undo changes made by another user and return to the previous version:

url: "/OData.svc/Root/Content/IT/Document_Library/Calgary('BusinessPlan.docx')/ForceUndoCheckOut",
type: 'POST'

Take lock over

Following lets administrators take over the lock of a checked out document from another user. A new locker user can be provided using the 'user' parameter (user path or id as string). If left empty, the current user will take the lock.

url: "/OData.svc/Root/Content/IT/Document_Library/Calgary('BusinessPlan.docx')/TakeLockOver",
  type: 'POST',
  data: JSON.stringify({
      'user': "12345"

Get version history of a content

You're able to get all the version history (current version, old minor and major versions, etc) related to a content at once. Following example shows you how:

url: "/OData.svc/Root/Content/IT/Document_Library/Calgary('BusinessPlan.docx')/Versions",
type: 'GET'

Restore an old version

It is also possible to recall an older version. In the next example you can see how you can restore a previous major version of a content:

url: "/OData.svc/Root/Content/IT/Document_Library/Calgary('BusinessPlan.docx')/RestoreVersion",
type: 'POST',
data: "models=[" + JSON.stringify({
    version: "V1.0.A",
  }) + "]"