# DOWNLOADPDF

#### Syntax

**DOWNLOADPDF**(*pageInfo*; *fileName*)

1. *pageInfo* - the name of the page which should be added to the pdf file, or a json text containing a list of pages to be exported - ***Value type**: text (optional, default value: current page name)*

   Possible values:

   * *text* - the name of the page which should be downloaded as pdf file
   * *json -* see the function [PDFCREATE ](/nedyx/clearlines-functions/import-export-functions/pdfcreate.md)for a detailed description of this option
2. *fileName* - the name under which the pdf file is downloaded - ***Value type**: text (optional, default value: the name of the current page or the first page name in the json text)*

#### Remark

* *fileName* can only be specified if *pageInfo* is specified as well.

#### Examples

**Example 1**

A click on the "Download PDF" button downloads the current page as a PDF file.

<figure><img src="/files/DxlxBhVZKmmZ2diWNZoa" alt=""><figcaption></figcaption></figure>

**Example 2**

A click on the "Download PDF" button downloads the page "Dashboard" as a PDF file with the file name "MyDashboard.pdf".

<figure><img src="/files/YOFXsbh3Ym05ea6UMmwf" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.nedyx.com/nedyx/clearlines-functions/import-export-functions/downloadpdf.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
