The version attribute is used to track the different versions of an element. The attribute has a set of numbers or characters that automatically increase based on changes in other attributes.
Setting
Name and description
Value
You can configure the following settings:
▪ Type: The type of version counter can be either numbers or strings.
– Numbers: Uses only numbers: For example, 1.0.0, 1.0.1, and 2.0.0.
– Strings: Uses letters for the first level and numbers for the second and third levels. Only 20 characters from following character set "ABCDEFGHJKLMNSTUVXYZ" are used to construct the first level version identifier. Character 'P' is reserved as a prefix for the second level and third level version identifier.
▪ Example of first level version identifiers: A, B, C
▪ Example of version identifiers with two levels: PA1, PA2, PB1
▪ Example of version identifiers with 3 levels: PA1.1, PB2.1
▪ Default Value: The default value is the value that the counting of the version number starts from.
– Major: 1.0 is the default value. If the type is Strings, the default value is A.
– Minor: 0.1 is the default value. If the type is Strings, the default value is PA1.0.
– Patch: 0.0.1 is the default value. If the type is Strings, the default value is PA0.1.
▪ Increased by attributes: Select how changes to other attribute values affect the version attribute.
– Major (1): The first number or string is increased
– Minor (0.1): The second number or string is increased
– Patch (0.0.1): The third number or string is increased
Version Synchronization
You can configure the following setting:
▪ Synchronize Patch Increases: Increases the Synchronize Patch increases.
Change Log
You can configure the following setting:
▪ Log Changes: Records each change of the attribute value.
Integration Settings
You can configure the following setting:
▪ Property URI: Provide a unique URI according to the Open Services for Lifecycle Collaboration (OSLC) standard for the attribute.
▪ Alias: Alias to use when you integrate with other tools. The default alias is an auto-generated random Universally Unique Identifier (UUID). You can change the alias, but it must be unique.
Example 1
These rules apply for a version attribute that is of the type numbers and that has a default value of major:
▪ If the value for all the attributes is none, the default value is 1.0, and the version number does not increase automatically.
▪ If the value is major for one or more attributes, the version is 1.0. When an attribute is updated, the version number increases to 2.0, 3.0, 4.0, and so on.
▪ If the value is minor for one or more attributes, the version is 1.0 and the version number increases to 1.1, 1.2, 1.3, and so on. The first level, which is the major level, is always 1 if it is not updated manually.
▪ If the value is patch for one or more attributes, the version is 1.0.0 and the version number increases to 1.0.1, 1.0.2, 1.0.3, and so on. The first level is always 1 if it is not updated manually. The second level is always 0.
▪ If the values for one or more attributes are major and minor:
For the major attributes, the version is 1.0 and the version number increases to 2.0, 3.0, 4.0, and so on.
For the minor attributes, the version number increases to 1.1, 1.2, 1.3, and so on.
▪ If the values for one or more attributes are minor and patch:
For the minor attributes, the version is 1.0.0 and the version number increases to 1.1.0, 1.2.0, 1.3.0, and so on.
For the patch attributes, the number increases to 1.1.1, 1.1.2, 1.1.3, and so on.
The first level is always 1 if it is not updated manually.
▪ If the values for one or more attributes are major and patch:
For the major attributes, the version is 1.0.0 and the version number increases to 2.0.0, 3.0.0, 4.0.0, and so on.
For the patch attributes, the version number increases to 1.0.1, 1.0.2, 1.0.3, and so on.
The second level is always 0.
▪ If the values for one or more attributes are major, minor, and patch:
For the major attributes, the version is 1.0.0 and the version number increases to 2.0.0, 3.0.0, 4.0.0, and so on.
For the minor attributes, the number increases to 1.1.0, 1.2.0, 1.3.0, and so on.
For the patch attributes, the version number increases to 1.0.1, 1.0.2, 1.0.3, and so on.
Example 2
These rules apply if a version attribute is of the strings type and has the default value of minor:
▪ If the value of all the attributes is none, the default value is PA1 and the version number does not increase automatically.
▪ If the value is major for one or more attributes, the version is PA1. When an attribute is updated, the version number increases to A, B, C, D, and so on.
▪ If the value is minor for one or more attributes, the version is PA1 and the version number increases to PA1, PA2, PA3, and so on. The first level, which is the major level, is always PA if it is not updated manually.
▪ If the value is patch for one or more attributes, the version is PA1.0 and the version number increases to PA1.1, PA1.2, PA1.3, and so on. The first level is always PA if it is not updated manually, and the second level is always 1.
▪ If the values are major and minor for one or more attributes:
For the major attributes, the version is PA1 and the version number increases to A, B, C, D, and so on.
For the minor attributes, the version number increases to PA2, PA3, PA4, and so on.
▪ If the values are minor and patch for one or more attributes:
For the minor attributes, the version is PA1 and the version number increases to PA2, PA3, PA4, and so on.
For the patch attributes, the number increases to PA1.1, PA1.2, PA1.3, and so on.
The first level is always PA if it is not updated manually.
▪ If the values are major and patch for one or more attributes:
For the major attributes, the version is 1.0.0 and the version number increases to 2.0.0, 3.0.0, 4.0.0, and so on.
For the patch attributes, the version number increases to 1.0.1, 1.0.2, 1.0.3, and so on.
The second level is always 0.
▪ If the values are major, minor, and patch for one or more attributes:
For the major attributes, the version is PA1 and the version number increases to A, B, C, and so on.
For minor attributes, the version number increases to PA2, PA3, PA4, and so on.
For patch attributes, the version number increases to PA1.1, PA1.2, PA1.3, and so on.