> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/codesys-hvac/en/codesys-projects/template-macro/macro-project.md).

# Macro project - Use

So that macros from the macro project can be easily copied into an empty project, it is recommended to follow this order:

1. Macro folder from the **macro project** copy and under *Macros* in the **empty project** paste.
2. Visu folder from the **macro project** copy and under *Visu* in the **empty project** paste.
3. Text list, alarms and alarm table from the **macro project** copy (adjust text list accordingly). From SP17 separately in the **empty project** paste.
4. Trend from the **macro project** copy and under *trend management* in the **empty project** paste.
5. Optionally from the program *PRG* the CFC page from the **macro project** copy and in the **empty project** paste.
6. Create the instance in the empty project
7. Search & Replace in the **empty project** all elements from point 1 to 4 (close all editors, only open the editors that should be changed, then change ALL opened editors - choose the correct selection in the search and replace function)
8. Place the appropriate object button on the Visu main menu (Start) page.


---

# 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://support.powerio.com/hub/codesys-hvac/en/codesys-projects/template-macro/macro-project.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.