Baseline Dependencies

When you select a Baseline on the 'Baseline Browser' tab, the three tabs in the lower half of the 'Reusable Asset Service - Baseline' view are updated with information from the Baseline. A Package might contain elements and diagrams that have relationships with objects in other Packages. When you generate a Baseline for that Package,  the name and Global Unique Identifier (GUID) of each Package containing these 'external' objects will be stored along with the Baseline and displayed in the 'Dependency' tab.

Note that Package A depends on Package B if any of these constructs (or their Tagged Values) in Package A reference elements in Package B:

• Elements
• Attributes
• Operations
• Operation Parameters
• Diagrams
• Connectors

Access

Open the 'Reusable Asset Service - Baseline' view using one of the methods outlined here.

Select a Baseline on the 'Baseline Browser' tab, then click on the 'Dependency' tab to display a list of dependencies for that Baseline.

Check Baseline Dependencies

Notes

• The Name and Global Unique Identifier (GUID) of a Package containing 'external' objects will not be stored with the Baselines if the option 'Check Package dependency when creating Baseline' is disabled on the 'Baseline' page of the 'Manage Model Options' dialog

Learn more

• Baseline Page
• Manage Baselines in Reusable Asset Service
• Reuseable Asset Service (RAS)
• Search Registry