Obtaining Cross-Model Dependencies Without a Repository Connection

If you anticipate needing to obtain information about cross-model dependencies with models not in your workspace in a situation where you will not have a repository connection, you can obtain this information in advance by checking your model out with the Check out dependencies option.

For models checked out with the Check out dependencies option (see Checkout Parameters) objects that are implicated in an impact or lineage analysis but that are not currently available display a red overlay in their bottom-left corner to indicate that the analysis cannot proceed beyond this point without connecting to the repository or otherwise obtaining the parent model. This option also ensures the cross-model dependencies appear on the Dependencies tab of objects even when the other models are not open in the workspace.

In the following example, the Employee table, which is generated from the Employee entity, is present in the analysis even though its model is not available, because the model from which the analysis was launched was checked out with dependencies: