> For the complete documentation index, see [llms.txt](https://support.who-umc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.who-umc.org/vigilyze/exports/export-case-in-pdf-file.md). # Export case in PDF file Case details can be exported that provide report information in PDF format suitable for review, sharing and archiving. #### To export case details in PDF file: 1. Open the “Cases” tab. 2. Select one or more reports. 3. Click **Export**. 4. Select **Case details**. 5. Open or save the PDF. The exported file contains detailed information for each individual report, with the level of detail depending on the information originally shared with VigiBase. #### When should I use a case details in PDF? Case details in PDF file are useful when you want to: * Review detailed report information * Share reports with colleagues * Include cases in assessment documentation * Archive reports outside VigiLyze #### Export limits A maximum of 500 reports for PDF and 50,000 reports for line listing Excel can be exported in a single operation. If your search contains a large number of reports, consider applying additional filters before exporting. {% hint style="info" %} To export a larger number of reports than the current limit allows, please contact UMC at . {% endhint %} --- # 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.who-umc.org/vigilyze/exports/export-case-in-pdf-file.md?ask=&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.