> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/elementy-aplikacji-artefakty/zarzadzanie-elementami-aplikacji/tworzenie-duplikatu-elementu.md).
# Creating an item duplicate
Creating a duplicate works analogously for each artifact type. For demonstration purposes, the process is shown below using the example of creating a duplicate of a form.
To create a copy, while on the list of the given artifact type (in the example module **Library**, tab **Forms**), click the context menu of this artifact and select the option **Duplicate**.
Figure 1. Context menu of the selected form
***
In the displayed window (here **Copy form**) we set the name of the new artifact (the name must be unique and comply with the rules described in: [*Save together with item publication*](/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/elementy-aplikacji-artefakty/zarzadzanie-elementami-aplikacji/zapis-wraz-z-publikacja-elementu.md)).
Figure 2. Artifact duplicate creation window
{% hint style="info" %}
You should remember good naming convention practices. For a form, the format is `prefixName` e.g. `kontoJuniorForm` (more in: [Naming conventions for application elements](/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/elementy-aplikacji-artefakty/konwencje-nazewnicze-elementow-aplikacji.md)).
{% endhint %}
---
# 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/elementy-aplikacji-artefakty/zarzadzanie-elementami-aplikacji/tworzenie-duplikatu-elementu.md?ask=&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.
