> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/jentis-dcp-elements/tags/multi-tag-edit/what-can-be-edited-using-the-multi-tag-edit.md).

# What can be edited using the Multi-Tag Edit?

With the Multi-Tag Edit Feature, you can easily update the common fields and their values on several tags simultaneously.

You have several options for customizing the data you input into these common fields:

1. **Variables**: Choose from four types of variables to insert into your fields.
2. **Text Inclusion**: Opt to include plain text if variable functionality is not required.
3. **Function Wrapping**: For more complex data manipulation, you can wrap variables with a function to perform specific operations or calculations.

   This flexible approach allows you to tailor the data entry process to meet the specific requirements of your tagging system efficiently.

However, you can not change the tags’ names, filters, or triggers. For that, you still need to access each tag and change it separately.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.jentis.com/jentis-dcp-elements/tags/multi-tag-edit/what-can-be-edited-using-the-multi-tag-edit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.