|
Version creation methods |
Scroll |
You can create dependent, dependent mirrored and independent versions of the model, using the Design Tree or Document manager.
The Versions tree is preferred for creating single versions. We recommend using the Document manager to create a set of several versions.
The composition and order of versions in the Manager duplicates the Versions tree. When adding a version in the Manager it will be added automatically to the appropriate place of the Versions tree.
By default, a model document contains only the main version. This will be the source version for the first created version. Later you can also use the versions created by the user for creating versions.
When creating a version, the name and the base part of the designation of the original version is inherited from the source version.
|
Specify the base part of the designation and the name of the main version before creating all other versions of the model (see section Version designation and name). |
The version number is automatically generated according to the setting and added to the version designation.
From any model version, except the mirror version, both dependent and independent versions can be created.
The created design, whether dependent or independent, inherits the geometry, design elements, variable set, and property values (including color and optical properties) from the original design.
|
Objects excluded from the calculation are inherited with the feature Excluded from the calculation. |
The procedure for creating an version when working with the Version tree is given in the Creating a version in the version tree section, and when working with the Versions control dialog — in section Creating a version in the version management dialog section.
In some cases, it is convenient to use a fulfillment set of an existing model to create a similar fulfillment set in another model. This method is described in the section Using another model's version list.
|
Creating versions in a model is not available if the model is a family template. To make the creation of versions possible cancel the use of the model as a template. |
See also
