🖨️ PDF generator: propform's own PDFs

propform can create PDFs itself from your form submissions — with no onOffice PDF Designer and no template maintenance. With one click you get a ready-made draft built from your form content, and you adjust design and structure directly in propform.

💡 The PDF generator is the simple alternative to PDF generation via onOffice templates. Both approaches can be used in parallel — per form, even at the same time.


Contents


Concept

When a form is submitted, propform renders the content into a DIN A4 PDF — with your logo, your fonts and colours. The PDF is processed via the familiar “Create & store file” pipeline: storage on the address and/or property record in onOffice, optional link field, email attachment, password protection and digital signature.

The template consists of blocks (headings, texts, field-value lists, images, signature areas …) that you arrange in a simple editor. The PDF preview button shows you the exact look at any time — what you see there is the real PDF.


Quick start: activating the propform PDF

  1. Open the form → section “Create & store file”
  2. Activate “Create & store file” and choose the storage location in step 2 (address and/or property) — this also applies to the propform PDF
  3. In the blue card “propform PDF (without onOffice template)”, enable the “Create propform PDF” toggle
  4. Done — on first activation, propform automatically generates a template from your form fields: sections become headings, descriptions become text paragraphs, fields become field-value lists, signature fields become signature areas
  5. Use “PDF preview” to check the result with sample data, and “Design template” to open the editor

⚠️ Without the “Create & store file” setting activated and a storage location selected, no propform PDF is generated.


Account-wide PDF design

Under Settings → PDF design, you define your default design:

  • Font and font for headings (all propform fonts available)
  • Font size (9–11 pt recommended, headings scale automatically)
  • Text, heading and accent colour (accent = lines and dividers)
  • Logo (URL, position left/centre/right, width) — appears in the header on every page
  • Header and footer text (onOffice macros are allowed in the footer, e.g. for company details)
  • Page numbers on/off
  • Handling of empty fields (hide or show with a dash)

Every form adopts this design as a starting point for its own PDF template. Changes to the account design do not retroactively affect existing form templates — so your forms remain stable.


Your own letterhead

Instead of the propform layout with logo and header, you can store your own letterhead — as a PDF or image (PNG/JPG). When creating the PDF, propform places it as a background under every page; the propform logo and header are then omitted automatically, because your letterhead brings its own header and design. Footer text and page numbers remain available as configured.

How to set it up:

  1. Under Settings → PDF design → Letterhead, upload your letterhead to the account library (name, first page, optionally a sheet for continuation pages) — the preview shows it immediately on a sample PDF
  2. In the form's template editor, choose one from the library under "Letterhead" on the right — or upload a letterhead there that applies to this one form only
  3. Use "PDF preview" to check the result with your content

First and continuation sheet: The first page applies to page 1 of the document. Optionally, upload a second sheet for page 2 and onwards (e.g. without the large letterhead header) — without a continuation sheet, the first page applies to all pages. Both files must be of the same type (both PDF or both image).

Page margins: You store default margins in millimetres on the letterhead — they determine where the PDF content starts and ends, e.g. below your letterhead header. Per form, you can additionally override the margins in the editor without changing the letterhead itself.

Good to know:

  • Allowed are PDF, PNG and JPG up to 10 MB per file; for images we recommend at least 2480 × 3508 pixels (A4 at 300 dpi) for a sharp print
  • Encrypted or damaged PDFs are rejected on upload with a clear message — re-save them (e.g. via "Print to PDF") and upload them again
  • If the letterhead is ever unavailable during creation, the PDF is automatically created in the standard propform layout — creation therefore never fails

Editing the PDF template (block editor)

Via “Design template” (or directly …/forms/{id}/pdf-template) you open the editor:

  • Left: block palette — one click adds the block to the end, or drag the block directly to the desired position in the document
  • Centre: your document as a sketch — sort blocks via drag & drop using the ⠿ handle, edit content directly in the cards, remove blocks with the ×
  • Right: design (can be overridden per form), content & attachments, document signature

Available blocks

Block Description
Heading H1–H3, with an accent line for H2
Text free-text paragraph, onOffice macros allowed
Field-value list table of fields (label + value): form fields with the submitted values and additional onOffice fields of the linked address/property record (even if they do not appear in the form)
Single field one field, optionally with its own label
Two columns two columns with their own sub-blocks
Image via URL, adjustable width/alignment/caption
Divider dividing line or spacing
Page break forces a new PDF page
Signature signature line; shows the signature from a form signature field or from the document view

The editor is deliberately a sketch (not a pixel-perfect view): it shows structure and content. The truth about the appearance comes from the PDF preview button — it renders the current draft as a real PDF, even before saving.


Content & attachments

  • Empty fields: hide (default) or show with a dash (–)
  • Embed uploaded images: images from upload fields appear directly in the PDF next to the respective field
  • Append uploaded PDFs: PDF files uploaded by the visitor are appended to the end of the document
  • Download fields: show the names of the files the field offers the visitor for download (for URL downloads, the download URL) — this way the PDF documents which documents were provided
  • Signature fields from the form are embedded as an image in the signature block
  • onOffice macros in text blocks, header/footer and in the file name are resolved during creation (property and address data of the submission)
  • More onOffice fields: below the form fields, the field picker offers all address and property fields of your onOffice — their values are read directly from the linked record during creation (visible as placeholders in the preview; without a linked record they remain empty)

The file name comes from “Create & store file” → File name (macros allowed). PDF protection and signature (step 3 of the section) also apply to the propform PDF.


Document signature: visitors sign inside the document

The highlight of the PDF generator: after submitting, the visitor can be shown the finished document and sign directly inside it — just like a real contract.

How it works:

  1. In the “propform-PDF” card (section “Create & store file”), activate the “Have the document signed after submission” toggle — alternatively in the template editor on the right under “Document signature” (there you also see the status as a badge)
  2. The template needs at least one signature block — if there is none, one is automatically appended when you activate the feature
  3. After submitting, the visitor sees the document with their entered data, signs with finger/stylus/mouse and confirms with “Sign & submit”
  4. Only with the signature does the complete processing run: contact/property are written, activities, appointments and tasks are created, emails and webhooks are sent, file uploads are processed and the PDF with the embedded signature is stored in onOffice

As long as it is not signed, nothing happens — nothing is processed and nothing is written to onOffice. This ensures that e.g. no onOffice auto-processes (triggered by activities) can start before the signature has actually been given. If the visitor does not sign within 72 hours, the submission is discarded — like an abandoned form.

Multiple signatures: The template can contain any number of signature blocks (e.g. “Tenant 1” and “Tenant 2”) — each becomes its own signature field in the document view. For each block you configure in the editor whether it is a required signature: the submit button only becomes active once all required fields (marked with *) have been signed; optional fields may stay empty. Without any required fields, the view acts as a pure review and confirmation page. The first automatically appended signature block defaults to required — unless your form already contains a signature field.

⚠️ Important rule: What the visitor sees is the final PDF. Values from the form are included immediately — they fill field-value lists and also replace simple field macros (e.g. _Vorname) in text blocks. All other macros (e.g. calculated fields or loops) are resolved against the current onOffice data: property data is available, but the new contact is only created after the signature. Values assigned by onOffice only at creation time (e.g. a new customer number) can therefore not yet appear in the document.

💡 The confirmation email, activity, webhooks and the submission notification to you also wait for the signature — the submission only appears in your submission list afterwards.


Frequently asked questions & pitfalls

Can I use the onOffice PDF and the propform PDF at the same time? Yes. Both sources use the same storage configuration and run in parallel.

Why is my propform PDF empty or missing fields? Empty fields are hidden by default. The preview uses sample data — the real PDF contains the submitted values.

Are macros resolved in the preview? No, in the preview macros remain visible as placeholders (there is no real submission there). In the real PDF and in the document view they are resolved.

Which fields do not appear in the PDF? Videos, link buttons and iFrames cannot be displayed in the PDF and are skipped; relation fields have no displayable value and are therefore not selectable. You can deliberately add hidden fields in the field picker (they are marked there).

What happens with very long forms? The PDF gets automatic page breaks; with the page break block you control them manually. Header, footer and page numbers appear on every page.