A version is a copy of a file at a particular time the file was checked into the repository. A new version can be created each time the file is checked in. Versions lets you keep track of changes to a file.
When you create or import a new file into the repository, it receives a version number of 1.0.
When you check in a file, you can decide whether to create a new version of the file or overwrite the existing version (You must have adequate permissions on the file to be given these choices).
Creating a new version gives the file a higher version number than it had when you checked it out, and also leaves a copy of the previous version in the repository.
Overwriting the existing version keeps the same version number on the file as the previous version, and does not save a copy of the previous version.
Depending on your configuration, you might be able to select whether to increase the version number by a whole number or by just a decimal point (that is, by a tenth). Increasing the version number by a whole number is considered a major revision; increasing by a decimal point is a minor revision. For example, if you check out version 1.0 of a file, and check it in as a minor revision, the file is stored as version 1.1. If you repeat this process, the file is next stored as version 1.2. If you then decide to check out the file, and then check it in as a major revision, the file’s version number jumps from 1.2 to 2.0.
The most recently checked-in file is marked CURRENT. File lists always display the current versions of files, unless you select to display all versions.
To display all the versions of a file:
Navigate to the file, and select it.
Select View > Versions.
To display all the versions of all the files in a list, select Show All Objects and Versions in the drop-down filter above the list.
You can work with an older version of a file using the same procedures you would use for working with any file in the repository.
If you edit an earlier version of the file, then when you check in the edited file, you are given these options:
You can check in the older version of the file as the new, current version. If you select this option, Webtop assigns the file a version number higher than the file’s previous current version.
You can check in the older version of the file as a branched version. This increments the older file by a new decimal-appended number. The incremented version becomes the current version in a new branch of version numbers. For example, if a user checks out version 5.0 of a document, edits it, and then checks it back in as a major version, the version number becomes 6.0. Version 6.0 is now the current version of the document. If another user then checks out, and edits version 5.0, which is no longer the current version, then when the user checks it back in, Webtop creates a new branch of the document, which starts with version 5.0.1.