> 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

ScribeWare can be used to fill in virtually any PDF form.   This walk through will show you how to configure it for your own forms.

## Overview

{% hint style="info" %}
**Using a ScribeWare form?** The Florida 4-Point, Wind Mitigation, Citizens Roof and WDO forms, the NPMA-33, and the Maryland and Texas WDI forms come already configured. Drag one in from the media bar's PDFs folder and click **Add missing fields**; see [Using PDF forms](https://docs.scribeware.com/into-the-weeds/using-pdf-forms.md). This walk through is for any other form.
{% endhint %}

In this walk through, you'll learn how to configure the [sections and fields](https://docs.scribeware.com/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scribeware.com/into-the-weeds/configuring-pdf-form-fills-in-scribeware.md?ask=<question>&goal=<user_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.
