Note: | You can also initiate this step by choosing the Actions button and then choosing the Add New Version command. |
In this field... | Specify... | ||||
Namespace | The namespace associated with this new version. This is of specific relevance for web service assets. The namespace given here reflects the target namespace defined in the associated WSDL file. A change of the namespace can be a differentiating factor between versions. Note that if you supply a new namespace here, you should ensure that the WSDL associated with this asset also reflects the new namespace. | ||||
System Version | In addition to the user-defined version, CentraSite automatically generates a System Version number. The system version number is independent from the version number you specify. The system version numbers are maintained for CentraSite's own internal use. CentraSite automatically assigns this version number when you create a new version of an asset. You cannot modify it. The version numbers assigned by CentraSite have the format <MajorVersion>.<Revision> and are always sequentially numbered starting from 1.0 (e.g., 1.0, 2.0, 3.0). The revision number is incremented automatically each time you modify the current version of the asset. | ||||
User Version - New | An identifier for the new version. You can use any versioning scheme you choose. The version identifier does not need to be numeric. Examples: 0.0a 1.0.0 (beta) Pre-release 001 V1-2007.04.30 | ||||
Organization | Specify the organization to which this new version will be added.
| ||||
Change Log | Optional. A comment or other descriptive information about the new version. | ||||
Propagate versions to dependent objects | (CentraSite only processes this checkbox for assets of type Service.) Mark this checkbox if you wish to automatically create new versions of all of the service's dependent schemas. The schemas will only be updated if you have permissions to modify them. |