> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/multi-language-and-text-tagging-support/text-tagging.md).

# Text Tagging

When turned on at the project level, this feature creates a GUID for text in a form part caption, conclusion etc. When copying the node, the Designer User can choose to maintain the link or to create another unique GUID for the copy. The choice has the following effect:

1. maintaining the link will insure that any changes to ONE of the linked nodes is immediately reflected in the second (and other linked nodes) in the Designer. Note that the change does not updated published packages
2. creating a separate GUID will insure the two nodes are independent, so edits to one node will NOT reflect in the other

Choosing to maintain the link is useful when content is re-used in multiple places (e..g the same advice is given for a number of different end points).


---

# 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://community-test.logicnets.com/release-9/platform-documentation/multi-language-and-text-tagging-support/text-tagging.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.