> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/into-the-weeds/configuring-pdf-form-fills-in-scribeware.md).

# Configuring PDF form fills in ScribeWare

## Overview

In this walk through, you'll learn how to configure the [sections and fields](/getting-started/scribeware-and-desktop-basics/understanding-chapters-and-sections.md) in a report template to pass data into your PDF form when your report is published. 

Broadly speaking, this process consists of: 

1. adding chapters, sections and fields to your ScribeWare template, that match the structure and form fields you wish to fill in on your PDF
2. Determine the *database name* of each form field in the PDF
3. Edit the corresponding field in ScribeWare, and configure it to fill in the pdf form with that field's value. 

The following pages will go over this process in detail.   You may want to work through configuring your form in small chunks to get used to how it works.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scribeware.com/into-the-weeds/configuring-pdf-form-fills-in-scribeware.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.