About Testing and Resolving Family Items

You can find additional information about the testing and resolution of Family items below.

This page discusses:

See Also
Testing and Resolving Family Items

Conditions to Resolve Family Items

This section provides you with information about the conditions required to resolve family items.

Note: The resolution is not required as it can occur on demand.

  • Standard Family: To resolve family items, the generic model must be specified as not editable using maturity changes. This guarantees that a user does not modify them and impact the whole family by mistake. For example, a user would resolve items and potentially modify the generic model. Further resolutions would contain modifications applied to the generic model but not on previously resolved ones. You can change the maturity of the generic model. A business rule defines the applied maturity transitions and the target maturity. To know more, see About the Maturity.
  • Design Family: No condition.

Ensuring Resolved Models Are Family-Owned

The system ensures that resolved models are owned by the family owner.

The family owner of an item model must resolve items. The system ensures that generated elements have the same owner as the family. If a user is not the owner of the family, a clear and automatic resolution is performed on a batch with the family editor or with the catalog. This batch resolution is made using the family owner's connection key.

  • The user's ID and role are encrypted in each family model and the connection keys are stored when the owner opens the family editor.

  • All or part of family items can be resolved on a massive batch. The batch is triggered within the family editor and does not block the user's tasks. A progress bar shows the batch status.

Note: Changing the family ownership changes, has no impact on the items ownership, that is they do not change owners.

Test and Resolve Items Dialog Box

You can test and resolve items dialog box.

The test and resolution operation can be performed on the whole family (All), on a selection (Selection) of items or on filtered items (Filter).

This dialog box allows you to resolve parts or all elements of the family. The resolution of items fails if the generic model is not at the target maturity. This command verifies that each resolved model is updated after all operations are applied in model resolution. If not, you are informed and the family item stores a status indicating that it cannot be used.

You can also decide to test items instead of solving them. Solving component family items is not mandatory. Once a components family item is saved in a catalog, it can be used, even if it is not already resolved.

When solving an item, if there is no error, the item status changes from (never resolved) to (resolved, up-to-date compared to the Generic Model revision), or from (resolved but out-of-date compared to the Generic Model revision). If an update error happens, the status of the item is (resolution failed) and it cannot be instantiated. A tooltip displayed on the element provides information about the error, and the level on which it occurred.

When a resolution is done on an already resolved but out-of-date item, a tree node appears under the given item, and a new line is added to the tree node thus enabling you to access old revisions of item. Those lines are identified by .

Users who are not family owners can perform resolutions using the family editor, with a batch resolution only. A batch using the user's ID is triggered if the user's item has not been resolved. This process allows you to resolve entire item libraries.

Furthermore, a progress bar showing the resolution process status appears. An error message appears if the user is not the owner.



Notes:

For existing annotations of generic models, a clean-up procedure is performed; it occurs chronologically as follows:

  • The broken imported geometries are deleted.
  • If the reference geometry of any annotation from the component family is not available, such annotation is considered as invalid and is deleted. When any view or capture is empty (there are no annotations are available in that view or capture), it is deleted.
  • Empty views and captures at the start are not deleted by the processing. Only the views or captures that are emptied when their embedded annotations are deleted by the cleanup process are deleted. The purpose of this function is to prevent deleting empty views or captures defined by the user to save, for example, a particular perspective of a 3D model.
  • All the annotations are automatically positioned for better readability.

Use Items only with Target Maturity

You can select only family items that have reached target maturity in resolved models to ensure that only elements that have been approved are used by other users. The Use Items only with Target Maturity option is available in the Preferences section of Component Family Definition.

A Component Family is an object that cannot be revised and whose maturity is not to be changed. The following features let you apply modifications on Family and Family Items that can be used in production in a non-impacting manner:

  • a dedicated setting ensures that only items at target maturity state are used.
  • a test mode is provided to generate items and to use them even if they do not meet the target maturity state.
  • a delete command is provided in the Family Editor to delete item models that may not satisfy defined criteria.

Target maturity is:

  • Defined in a business role to adapt to customization.
  • Reached when using automatic maturity change mode.
  • Achieved with the automatic maturity command in the Family Editor.

If one or more revisions of resolved models are present, Use Items only with Target Maturityapplies the latest revision that has reached a Target Maturity state. In the absence of a Target Maturity state, the command uses the latest revision and issues the following warning:

  • No revision of resolved model with Target Maturity is found. Using latest revision of resolved model.

Note: This option is also applied during the On Demand generation of items from the Catalog and the Product Table. You can use items with any maturity when this preference is disabled.