A Document Solution is the top-level pipeline that ties a Data Source to one or more Document Templates. On its own, a Document Solution defines what gets generated — which template, fed by which data.
How it gets generated — output format, processing mode, storage destination, locale — is defined separately, in a Document Solution Configuration.
This separation means the same Solution can be triggered in different ways without duplicating the underlying template-and-data pairing — useful when you need the same content delivered as a synchronous PDF in one scenario and an asynchronous DOCX in another.
| Setting | Description |
|---|---|
| Data Source | Defines where the data for this Solution comes from |
| Templates | One or more Document Templates the Solution can render |
A Document Solution can have multiple Document Templates associated with it — useful when the same data pipeline needs to produce different layouts or formats on demand. See Data Sources for how the Solution's data is structured.
See the full set of solution endpoints in the API Reference.
A Document Solution can have multiple Configurations — each one a named, independent variant of how generation should run. A single Solution might have one configuration for a fast synchronous PDF export and another for a high-volume asynchronous DOCX batch job, both pulling from the same template and data.
| Setting | Description |
|---|---|
| Output Format | The format of the generated file (PDF, DOCX, XLSX, etc.) |
| Processing Type | Synchronous or asynchronous generation |
| Delivery Method | How the generated file is delivered once ready |
| Path | Storage destination for the generated file |
| Locale | How dates, numbers, and currencies are formatted in the output |
| Language | Which Template Label translation set to apply |
| Time Zone | The time zone applied to date and time values in the output |
When creating a Document Request, you can target a specific Configuration.
Doctavian supports two processing modes, configurable per Configuration:
Processing status simultaneously without blocking each other. Recommended for most integrations.Every time you trigger generation, Doctavian creates a Document Request — a job record that tracks the generation from start to finish, referencing the Template, Data Source, and optionally the Configuration used.
Document Requests move through five statuses: New, Processing, Completed, Error, and Canceled. See Error Handling for what to do when a request ends in Error.
See the full set of request endpoints in the API Reference.
When creating a Document Request via the API, the key inputs are:
On completion, the Document Request record holds a reference to the generated file in the configured storage destination.
Uploaded template and data files are deleted after a Document Request is processed — regardless of whether generation succeeded or failed. If no request is triggered, files are automatically deleted at midnight. Download or store any files you need before triggering generation.
Ready to put this into practice? See Generate Document for a complete end-to-end walkthrough.
Batch mode can improve performance over the default Google App Script sequential mode.