This article pertains to the legacy version of Dependency Map, which is deprecated. For information on the current version, please visit the Dependency Map Knowledge Base article.

The dependency map is one of the best views to show dependencies across or inside workspaces.

One popular use case is showing applications and processes that support specific Capabilities as shown below.

Ardoq dependency map

In this example we see the capabilities colored blue (this is our context), applications colored orange, and processes colored blue (globe icon).

We can apply conditional formatting on top of this to highlight information from fields, for instance, Status (Planned, In Production, Planned Sunset, and Terminated) as shown below. See the same view, with statuses on the applications. Salesforce is planned sunset, and webshop is Planned.

Ardoq dependency map status

By default, this view shows components and their parent-child hierarchy in horizontal lanes. Outgoing references are shown as rounded rectangles.

Note that with grouping applied the view behaves differently.


Highlights the selected component and Workspace you are in.

View modifiers

Ardoq dependency map options



Color by reference

Colors the references according to the color of the reference

Include reference parents

Includes the parents of referenced components

Show vertical

Flips the layout to a vertical layout

Show reference labels

Shows reference labels in the reference items, by default this is display text but can be set to render the reference type in perspectives (see formatting)


Changes the functionality of the view substantially. References are not shown, and the components in the dependency map are shown according to the grouping rules.

Limits on the number of components/references

1000 components, if there are more the whole visualization will try to render compacted (with limited functionality).

Did this answer your question?