> 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/filling-your-pdf-form-with-field-specific-information.md).
# Filling your PDF form with field-specific information
Any information that isn't provided as "[commonly used" information](/into-the-weeds/configuring-pdf-form-fills-in-scribeware/filling-your-pdf-form-with-commonly-used-information.md) can be filled from your [PDF form fields](/into-the-weeds/configuring-pdf-form-fills-in-scribeware/adding-pdf-form-fields-to-your-scribeware-template.md)!
Referring back to our example from earlier:
## Checkboxes
We want to tie the first 3 checkboxes to the corresponding checkboxes on the PDF form:
1. Edit the section
2. Click on the field to edit
3. click on "PDF Forms"
4. Enter the [Database Field Name](/into-the-weeds/configuring-pdf-form-fills-in-scribeware/uncover-your-pdfs-database-field-names.md) of each of the field names
## Text fields
Similarly, plain text fields can be filled via the 'free form' text entry at the end of each field:
## Date fields
If your PDF form contains field that look like this
It's actually configured as 3 separate fields, each with their own Database Field names. Configure it in ScribeWare as \/\/\:
{% hint style="info" %}
Dates must use "/" as the separator.
{% 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://docs.scribeware.com/into-the-weeds/configuring-pdf-form-fills-in-scribeware/filling-your-pdf-form-with-field-specific-information.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)