This functionality is only available for certain module packages.

You are here: EEC > BASE > Basic workflows > New creation of discipline-specific components in the library > Resources and their management

Resources and their management

Resources can be managed either externally in the file system or internally in the model.

The resource path validation displays the input of an invalid path in the editor as an error. Outside of editors (e.g., EOX Import), this is displayed as a warning.

To allow for an integrated versioning not only of the components, but also of the referenced resources, it is possible to manage (internalize) the resources also internally, i.e., in the model.

The state graph of the following graphic shows the states that a component can adopt with respect to the resource, and which changes are possible:

Assigning resources is not meaningful in the case of abstract components. Their state, therefore, is No resource.

A component can be assigned an external resource. In this state, the component is merely assigned a path to the external resource. Alternatively, it is also possible to save the resource in the model (Resource internal).

As illustrated in the graphic, it is possible to modify the state of a component in such a way that an external resource is converted to an internal resource (internalize) or an internal resource to an external resource (externalize).

Independently of this, a resource can be imported as new for an existing component (import). Both for internal and external resources, it is possible by analogy to export a resource to a file system.

Whether a resource must be managed internally or externally is defined separately for each discipline (except text discipline) using a model variable. The following figure shows the corresponding specification for the ECAD discipline:

The appropriate differentiation must be selected for text disciplines on the Attributes page of a TextDisciplineConfiguration:

Existing external resources are internalized via the context menu in library views using the following action:

It is possible to internalize entire libraries or only individual files.

The Attributes page of the components has been extended in such a way that the three possible states of resources, and the respective actions that are possible, are represented in a transparent manner:

Information:

The consistent versioning of models requires that all external resources be internalized in the model.

More: