Resolving Elements Example

Example 1:

There are many ways in which unresolved elements can be created. This example describes how an unresolved element is created through inheritance and it can be resolved.

A developer working on a part of an application creates a class, called Class B which inherits from Class A. That is, B has a dependency on A. Class B is in another part of the application and therefore has a different VersionFile from Class A. The developer checks in the classes for version control. A second developer wants to work on Class B and checks it out. During the import of the class a warning is shown that the target for the 'Inherits' property of the Class 'ClassB' is required but does not exist in the Model or in the Interchange File. Class B is displayed in the model and shows that it inherits from Class A which is listed as unresolved.

The parameters of Class A (including its stereotype) aren't known, so Class B only has those parameters that override Class A's parameters. The second developer has three choices:

Example 2:

This example describes how an unresolved element is created due to a poor merge operation and how it can be resolved.

When you perform a get latest recursive on a model created after a poor merge, unresolved elements are created for the missing version file while synchronizing the database with the workspace. Some of the elements in this model templates to the unresolved element created after the get latest operation.

To resolve this, delete the unresolved element from the model permanently and check in the pending changes. Now, perform a get latest on the model. The unresolved element is resolved.