> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/appian/template-generation.md). # Template Generation - [Template generation in Appian](https://docs.apryse.com/appian/template-generation/template-generation.md): Generate dynamic PDFs with Apryse's office template generation framework. Design templates in Office documents and merge data with ease using Apryse SDK. Explore loops, conditionals, images, and more. - [Sample App - Generating invoices in Appian with WebViewer](https://docs.apryse.com/appian/template-generation/sample-docgen-app.md): Learn how to generate invoices in Appian using WebViewer. This guide walks you through creating a PDF invoice from an Appian data entity with placeholders. Perfect for those familiar with Appian Desig --- # 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://docs.apryse.com/appian/template-generation.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.