> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/designer/work-in-the-app/elements-used-in-diagrams.md).

# Elements Used in Diagrams

How to use ServiceNow elements or specific Configuration Items (CI)

An additional benefit of running Designer natively on ServiceNow is the ability to see in which diagrams a specific element or Configuration Item (CI) is used.

We have created 2 related lists which needs to be added to the form view in ServiceNow:

* **Designer Diagrams**: Shows the Diagrams directly referred through the Diagrams Form manually
* **Designer Diagrams Usage**: Shows the Diagrams used in a Diagram automatically

**A** – Each Diagram can be linked to an Element via the Document ID in the diagrams form field called Related Element.

**B** – Ensure, that the related list Designer Diagrams is visible in the Form.

**C** – All associated models are visible in the related list within the form.

**D** – By making the Designer Diagram Usage related list visible in a CI's form, you can see in which diagrams a specific element (CI) has been used.

**E** – The related list tab in the form shows all diagrams, where the element (CI) has been used.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ins-pi.com/designer/work-in-the-app/elements-used-in-diagrams.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.