# Load Dependencies

This article explains how the Designer application in ServiceNow enables the loading of various relationship types and dependencies.

The Load Dependencies feature in ServiceNow's Designer application allows users to visualize the connections between objects in their data, providing the ability to generate diagrams based on upstream and downstream relationships or references, related lists, and hierarchy. Users can also add custom filters and save unique settings as presets for future diagrams. The diagrams include labels describing the relationships between elements, such as parent-child, related list, and reference.

## Custom Filters

You can also add custom filters to concentrate diagrams on particular elements and relationships.

## Saving Presets

After you've created your unique settings, you can save them as presets for easy access when creating future diagrams.

![rn-update2](/files/hjbNpvHJ0WTKjYV1ILEQ)

## Setting Favorites

Additionally, you can set specific presets as favorites, making them directly accessible from the element in any diagram.

![rn-hmaps-update6](/files/MsLcNRnm5tv4irhduoIJ)

## Connectors Labeling

For easy reading, diagrams include labels describing the relationships between elements. The relationships are:

### Relationships

The connector formatting will align with the **Relationship Definitions** defined.

### Parent and child

The following example shows the styling of **parent and child** connectors.

### Related list

The following example shows the styling of **related list** connectors.

### References

The following example shows the styling of **reference** field connectors.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ins-pi.com/designer/work-in-the-app/load-dependencies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.