HTML template rendering

Pdfless holds HTML templates with placeholders that map to fields in your data. When an event calls for a document, a Beam agent chooses the right template, reads the record values it needs, and passes them into the layout for rendering following the mapping a customer set. The returned PDF is saved to the destination the rule names, and the requester is told it is ready. Records with empty placeholders, malformed values, or a template the agent cannot match are held back and handed to a person, who resolves the data before rendering runs.

Batch document generation

Repetitive runs, such as monthly statements or bulk certificates, feed many records through one Pdfless template. A Beam agent takes the approved batch, reads each row, and renders a document per record while noting successes and failures. Finished files are written to storage and a summary goes to the owner. Rows that fail validation, exceed a size limit, or point at a missing asset are separated from the run and reported to a person, who decides whether to correct the input or skip those records before the agent reprocesses them.

Template version control

Each Pdfless template can change over time, and documents should render from the version your team approved. A Beam agent checks that a request references the correct template version, reads the associated data, and renders only when the two agree with the rule in place. Output is filed and the requester notified. When a request points at a retired template, an unapproved draft, or a version mismatch, the agent stops and alerts a person, who confirms which template should be used before any document is produced.