# Attach Document

> `UiPath.Testing.Activities.AttachDocument`

`UiPath.Testing.Activities.AttachDocument`

## Description

Attach documents to your test execution results to have proof of the outcome. You can view the attachment in Orchestrator by navigating to **Testing** > **Test Executions** > **Test Run Details** and then selecting **View attachments** on a specific test case.

:::note
* The attachments are available only if you run the workflow as a test case. If you run it as part of a job, the attachment
is unavailable.
* Attachment preview in Orchestrator is available for JSON, TXT, XML, PNG and JPEG file formats.
:::

## Project compatibility

**Windows - Legacy | Windows | Cross-platform**

## Windows - Legacy configuration

### Designer panel

* **File** - Specify the file path of the document that will be attached to the test case, or browse for the file on your machine.

### Properties panel

#### Common
* **DisplayName** - The display name of the activity.

#### Input
* **File** - Specify the file path of the document that will be attached to the test case.
* **Tags** - Set custom tags to the attached document.

#### Misc
* **ContinueOnError** - Specifies if the automation should continue even when the activity throws an error. This field only supports Boolean values (`True`, `False`). The default value is `False`. As a result, if the field is blank and an error is thrown, the execution stops. If the value is set to `True`, the execution of the project continues regardless of any error.
* **Private** - If selected, the values of variables and arguments are no longer logged at Verbose level.

## Windows, Cross-platform configuration

* **File** - Specify the file path of the document that will be attached to the test case.

### Advanced options

* **Tags** - Set custom tags to the attached document.
* **ContinueOnError** - Specifies if the automation should continue even when the activity throws an error. This field only supports Boolean values (`True`, `False`). The default value is `False`. As a result, if the field is blank and an error is thrown, the execution stops. If the value is set to `True`, the execution of the project continues regardless of any error.