Make an Attached Form Fillable
Turns the blank form attached to the package into a form the fill can use, converting it first when it has no fillable fields.
Overview
The blank form you attach is often a scan or a print-to-PDF with nothing fillable in it. This is the step that turns the file into a form, and it takes both kinds without being told which one you have: a PDF that already carries fields is registered as it stands, and a flat one goes through the same flat to fillable conversion the conversion tool runs.
The conversion happens inside the call. The agent does not hand you a job to come back to later, it waits and then either has a form or tells you why there is none.
What It Does
| Capability | What it means for you |
|---|---|
| A fillable PDF is taken as it is | A form that already has fields needs no conversion and is ready in one step |
| A flat PDF is converted | A form with no fillable fields is converted before anything else happens to it |
| Page and field count come back | The result says how many pages the form has and how many fields it ended up with |
| It joins your forms library | The form is listed among the ones you uploaded, so a later package fills it without attaching it again |
| Fine-tuning does not hold it up | A form that arrives fillable is handed over at once, and the work that sharpens its filling runs behind |
| A conversion that outlasts the wait is not stopped | The run reports that the form is not ready yet, and the conversion carries on |
When the Agent Chooses This Tool
Available in the Fill Any Form workflow. The appraisal-report, pre-bid and coating QA workflows do not have it.
The instructions call it once in a run, on the one attachment it decided is the blank form.
- A form already in your library skips this step and goes straight to the fill: it is a form already.
- A file that cannot become a form ends the run with the reason in one plain sentence, and the agent is told not to try the same attachment again.
Inputs and Outputs
Takes: one attachment of this package.
Returns: the form for the fill to use, with its page count and field count, or the reason the file cannot become a fillable form.
Example
A client attaches a scanned credit application and nothing else.
The agent names the package after the form and calls this on it. The scan is converted, and the agent comes back with a form of four pages and sixty fields. There is nothing to fill it from, so the run asks for the data instead of filling, and says the form is now in the library.
Limits
- One form per run. The workflow's instructions allow a single ingest in a run.
- The wait has a limit. A conversion still running when it runs out is reported as still converting, which is a different answer from a file that cannot become a form at all.
- An attachment that cannot be read is refused. A file that is not in this package, or whose bytes cannot be read back, comes back as a refusal rather than a guess.
- A form the conversion left without fields is not in the library. The library lists what can be filled, so a file that came out of conversion with nothing on it is not offered for a later package.
FAQ
My form is a scan with no fillable boxes. Does that work?
Yes. A PDF with no fillable fields is converted in the same run, before the fill, and the agent waits for the conversion rather than asking you to come back.
Do I have to attach the same form again next time?
No. It is in your forms library afterwards, and the agent can find it there by name and fill it without an attachment.
What happens if the conversion takes longer than the run?
The run tells you the form is not ready yet. The conversion is not stopped, so a later package finds the form in your library.