The versioning system maintains two types of version numbers:
Base version number: The latest checked-in version of the asset. When an asset is created, its initial base version number is 1.
Potential version number: The version number that is conditionally assigned to each checked-out version of an asset.
When you add an asset to a project, the system assigns it a potential version number. When the project checks in its asset, the system converts the potential version number to the new base version. If another project checked in the same asset earlier, the system assigns the next available number to the new base version.
For example:
John adds the asset ExecProfiles to his project. ExecProfiles is new to the versioned repository, so it has base version number 1. When John adds ExecProfiles to his project, the system assigns his working version potential version number 2.
While John is editing ExecProfiles, Susan also adds this asset to her own project, which gets potential version number 3.
Susan deploys her project and its assets are checked in, including ExecProfiles. The system uses its potential version number and renumbers the base version number as 3.
John gets an alert that tells him a conflict exists between his version of ExecProfiles and the new base version that Susan checked in. John can resolve this conflict either by overriding the base version, or by merging the two conflicting versions (see Resolving Asset Conflicts).
John deploys his project and its assets are checked in. The system increments the base version number of ExecProfiles to 4.
To view an asset’s version number, display the Assets tab and examine the Base Version and Current Version columns. For more information, see View Project Assets.
More detailed information about an asset’s version history is available in the Assets > History tab. For more information, refer to Viewing an Asset’s History.
