| Prev | Next |
Package Dependencies
A Package held as an asset in the Reusable Asset Service registry might contain elements and diagrams that have relationships with objects in other Packages. The Packages containing these 'external' objects will also have been added to the Registry to support the first Package, and will be listed in the 'Registry Browser' tab along with other (unrelated) Packages. You can establish whether the selected Package in the 'Registry Browser' tab has links to other Packages in the Registry, and which they are, by reviewing the 'Dependency' tab.
Package A depends on Package B if any of these constructs (or their Tagged Values) in Package A references elements in Package B:
- Elements
- Attributes
- Operations
- Operation Parameters
- Diagrams
- Connectors
Access
Open the Reusable Asset Service window using one of the methods outlined here.
Select a Package, then click on the 'Dependency' tab, to display a list of Dependencies for that Package.
|
Ribbon |
Publish > Model Exchange > Reusable Assets |
Check Package Dependencies
Option |
Detail |
See also |
|---|---|---|
|
Package |
Displays the name of the related Package. |
|
|
Version |
Displays the latest registered version of the related Package that has links to the selected Package. |
|
|
GUID |
Displays the Global Unique Identifier of the related Package. |
|
|
Find in Project Browser |
Right-click on the 'Package' line and select this option to see if the Package also exists in your model and, if it does, to highlight it in the Browser window. |
Notes
- If one Package depends on another, and that second Package itself depends on another Package, both the second and third Packages are shown in the 'Dependency' tab
- The 'Dependency' tab will be empty for a 'Learning Center Library', 'Reference Data Library' or 'Source Code Library' type Storage