> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/modules/reporting/template-options.md).

# Template - Options

> UPDATED: Please head over to our new GitHub Support Site for help, examples, tips and tricks: <https://github.com/AttackForge/ReportGen>

## RemoveDuplicateEvidence

This option can be set at the beginning of your template in order to remove duplicate Evidence for vulnerabilities which have already used/displayed the evidence within the Proof-of-Concept or Notes for any of the affected assets, for example the images have already appeared in-line within the Proof-of-Concept or Notes.

```
{#$optionRemoveDuplicateEvidence}{/}
```

This option is useful to reduce duplicate evidence displaying, significantly reducing report size and making content more useful to the reader.

#### How it works:

When looping over `{#affected_assets}` - if the Proof of Concept or Notes includes an inline image - this image will be removed from the {#evidence} section to avoid duplication of displaying the same evidence file.

Example:

**!IMPORTANT: You must include {#$optionRemoveDuplicateEvidence}{/} tag at the beginning of your template file.**

```
{#$optionRemoveDuplicateEvidence}{/}
...
{#vulnerabilities}
VULNERABILITY: {title}
{#affected_assets}
ASSET: {asset}
NOTES:
{#notes_html}
{@note_styled(“image_description”:“caption”) | resize:[“400”]}
{/notes_html}
PROOF OF CONCEPT:
{@proof_of_concept_styled(“image_description”:“caption”) | resize:[“400”]}
{/affected_assets}
{#evidence}
{%fileBase64 | resize:[“400”]}
{fileName}
{/evidence}
{/vulnerabilities}
```


---

# 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.attackforge.com/app/modules/reporting/template-options.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.