Creating a Model Version Revision or Derivation Branch

You can create a revision of a model version. You cannot revise a model version if that model version already has a revision. You create a revision when you create the root model version for a model. You can also create a revision or branch of a model version.

Note: If you manually add a variant, option group, variant value, or option to a model version and then add it as a design variant to a logical feature, that variant, option group, variant value, or option is retained in the model version context even if the design variant is removed.

Before you begin: Open the Model Version Derivations page for the model version revision. See Model Version Derivations Page.
  1. If the new model version revision or branch will be based on an existing model version in the list, select that model version.
  2. From the toolbar, select Actions > Create Revision. You can also click Create Branch as long as a root model version's revision already exists. The first model version on the Model Version Derivations page must be a revision.
  3. Edit these details:

    Field Name Description
    Basics:
    Type Shows the type of model version being created. Revisions and branches must be the same model version type as the parent model version. If this model version is the first one for a model, click to select the type:
    • Software product
    • Hardware product
    • Service product

    Your company may have defined additional types or subtypes of model versions.

    Name Initially shows the name of the source model version. Edit for this revision or branch.
    Revision Initially shows the next sequential revision. You can edit the value by entering a revision value. Both model version revisions and model version's branches require a revision value.
    Tags Type one or more tags to assign to the new revision or branch. Separate multiple tags with commas without spaces (for example: Alpha,Beta,Delta). Tag names must comply with DesignSync naming rules.
    Note: The maximum length of name strings varies for different databases. The maximum length for SQL Server is 127 characters. The maximum length for Oracle is 127 bytes. The number of bytes per character depends on the database setting for character encoding. Thus, for Oracle, the character count will be less than for SQL Server if some characters are multibyte. The same is true for all string values stored in the database.
    Tags Comments Type a single comment that applies to all of the tags specified above.
    Description Enter a meaningful description of the revision or branch.
    Policy If your company implemented subpolicies, select the policy from the list.
    Derivation Details:
    Derivation Type The Branch or Revision (depending on which command you selected). This field is not editable.
    Derived From The selected source model version. This field is not editable.
    Derivation Level

    Revisions are required to be in the main release structure, so the derivation level cannot be changed.

    For branches, the possible values depend on the type of model version.

    For hardware or service products:

    • Main Release
    • Fix Release

    For software products:

    • Release
    • Fix Pack
    • Hot Fix
    Merged From Click to select one or more model versions that have been merged into the new revision.

    This value must be different from the value used for Derivation Context.

    Additional Information:
    Marketing Name Initially shows the same name as the source model version. Edit for the revision or derivation.
    Marketing Text Initially shows the same text as the source model version. Edit for the revision or derivation.
    DesignSync Connection:
    • If the first revision of the model version has a DSFA connection, then the following fields are initialized with the DSFA connection information from that revision, except for the Selector field, which is left blank (because it is assumed that each model version revision will be connected to a different revision of the DesignSync object).
    • If there is an existing DSFA connection, only the Selector field is editable. Otherwise, all fields are editable.
    Store Shows a list of DesignSync stores. Choose one from the list.
    Path Type or click to select the path to the object (below the store) to be connected to.
    Select the type of DesignSync object to be connected to. If you specify the path, this is defined automatically.
    • File
    • Folder
    • Module
    Selector Enter a selector or leave the default (Trunk:Latest) as is.

  4. Click OK.

If a tag of the same name already exists on another revision of the model version, the tag is moved to the new revision. All variants, variant values, option groups, and options associated with the original model version are replicated to the new revision. If the original model version had expression rules and matrix rules defined, these are shared with the new revision.