Managing Component Family Modifications

You can create a revision of the generic model.

Notes:
  • Standard families: The Manage Component Family Modifications command works only if a new revision is available. The collaborative space rules driving the maturity level require an appropriate maturity level to create new model revisions. This is true when:
    • The maturity of items has not been changed automatically or manually.
    • The maturity change is done, but the Business Logic maturity level does not match the new revision maturity level.
  • Design families: The modifications applied can be based on the current revision or another one if available. It proves particularly useful for table modifications because model modifications (adding or removing rows) are always taken into account.
Warning: Minor revisions are not taken into account neither for standard nor for design families.

See Also
Creating a Generic Model
  1. Click Manage Component Family Modifications .

    The Apply new revision of the generic model dialog box opens.

  2. From the Available revisions: list, select the revision, --A in our example.
  3. Select the option you want to apply in the Generic model versioning impact box: Only the design table was modified (partial impact) or The model was modified (all items impacted).
    Notes:
    • The choice of the option depends on the modifications that were performed on the new revision of the generic model. If only the table was modified, selecting Only the design table was modified (partial impact) guarantees that the impact on the family is minor:

      • New items appear if new rows (or new identifiers) are found.

      • Previous items are deleted if old rows (or identifiers) have been removed. Note that only the family item is removed. The associated models are kept in database.

      • Items are specified as not up-to-date (if previously generated) if the values of the corresponding row have changed.

      • Once a revision of the new component family generic model has been applied, new resolved items become new revisions (duplicated revisions) of items that have been previously resolved. These new items appear on a row in the same table, see limitations.

      If the model has been modified, all items are impacted.

    • An error message appears if no other revision of the generic model exists.
  4. Select the option you want to use in the Items update method: Do not impact previously generated items, Create new revisions of previously generated items or Overwrite previously generated items.
    Notes:
    • Do not impact previously generated items: You can choose not to impact previously generated models, whatever the modification applied to the generic model. This option is available if you created a Design Family.
    • Overwrite previously generated items: Be cautious when using this option as it modifies the objects stored in database whatever their maturity state. The objects can be overwritten even if used in assemblies and in "released" state. This option is always available even if the modifications performed on the generic model are impacting: No modification of the structure is accepted, which means that you cannot modify the product structure. If this mode is required, and if the structures of the generic model and the previously generated model are not compliant, the standard mechanism for creating revisions is used.

      When overwriting models:

      • Overwrite operation occurs in database.
      • The identifier set is not modified.
      • The maturity of the components is reset to its initial state.
      • Links in assemblies containing instances of overwritten models are not impacted. Links do not have to be rerouted.
      • Assemblies containing instances of overwritten models are not up-to-date after this operation whatever the modifications performed on the generic model.
      • The overwrite operation cannot be performed in session if the component to overwrite is loaded in session. The system automatically detects this case and uses the batch resolution. In the family tab, if Test & resolve is used, the batch resolution option is automatically selected and grayed out if one of the items to resolve is loaded in session.
      • For batch resolution, if the previous generated element components are loaded in session, those elements are not refreshed after the batch execution. The changes are visible when unloading and reloading those models (or assemblies containing them).

  5. Click OK.
    Your generic model is modified.