🧩 Macros — propform & onOffice

Macros are placeholders that are replaced with actual values at runtime — e.g. the first name of a loaded address, the UUID of a property, or the current date.

Contents

• Where can macros be used?
• Standard onOffice macros
• propform-specific macros
• Loops — Search criteria loop
• Loops — Calendar loop
• Loops — Address loop (buyer / owner)
• Pre-macros (accessing linked records)
• Direct access to contact type link

Where can macros be used?

| Location | Macros active? | |--------|---------------| | Form heading / subheading | ✅ | | Field label, hint, placeholder, tooltip | ✅ | | Default value, required value | ✅ | | Description fields (special type) | ✅ — incl. propform macros such as _pfButton, _pfLink | | Activity note | ✅ | | Task subject & description | ✅ | | Email recipient, CC, BCC | ✅ | | Email subject & body | ✅ | | Thank you page URL | ✅ | | “Write values” target values | ✅ | | File upload field name | ✅ | | Link button URL | ✅ | | File download custom name | ✅ |

## Standard onOffice macros

You can find the complete official list of macros in the onOffice Help.

> ⚠️ Note on naming conventions: onOffice is inconsistent regarding upper and lower case. Address macros are usually in CamelCase (first letter capitalised), whilst property macros are lower case. Stick strictly to the official naming convention — otherwise the macro will not be resolved.

Address macros (CamelCase)

Property macros (small)

Date & Time Macros

Function macros (conditions, calculations)

> 💡 _ifEmpty with user fields — multi-office pattern: If each location/office has its own review link, telephone code or similar, create a custom field for the user (e.g. Benutzerzusatz1Name) and use: _ifEmpty(_OBJBetreuer_Benutzerzusatz1Name;"https://fallback-link.de";_OBJBetreuer_Benutzerzusatz1Name) — if the supervisor has left the field blank, the fallback applies. Shorter and more readable than _calculate(IF([feld]=null;"a";"b")) for simple empty checks.

User macros (employee performing the action)

propform-specific macros

These macros are only available in propform.io — not in standard onOffice. They work in forms as well as in activities, tasks and emails written via propform (macro resolution mode “alternative” in onOffice).

Buttons & Links in Description Fields

Examples:

_pfButton("Weiter zum Formular", "https://example.com", "rounded-pill", "_blank")

_pfLink("https://example.com", "Hier klicken", "_blank")

Search criteria macros

> 💡 Self-service pattern for search profiles: These three macros, together with _pfButton(...) and the loop _bScRek_("status:1"), form a complete self-service workflow: Overview email lists all active search profiles + one-click buttons for editing/deactivating. Complete setup under Edit / deactivate search profiles.

File path macros (for images/signatures in PDF templates)

Parameters:

• Field name: internal onOffice field name of the file field (e.g. unterschrift_kaeufer)
• Width: value in the selected unit (e.g. 400 — default value for signatures)
• Height: either a fixed value or variabel for auto-height
• Unit: px or mm
• Type: mail or html

Example — embedding a buyer’s signature:

_dateipfadAdressfeld(unterschrift_kaeufer;400;variabel;mail;html)

Multi-sig pattern for multiple buyers/owners:

Within the address loop (_buyerbrek_1_ … _buyererek_1_, see below), you can embed a separate file field with a signature for each buyer. If not all buyers have signed yet, always wrap with _ifEmpty(...) — otherwise a gap will appear in the PDF:

_buyerbrek_1_
_BuyerVorname _BuyerName
_ifEmpty(unterschrift_kaeufer;"";"_dateipfadAdressfeld(unterschrift_kaeufer;400;variabel;mail;html)")
_buyererek_1_

> 💡 File field availability: File path macros only work if the file is located in an onOffice file field of the record — not in the general ‘Files’ tab. The file field must be created in onOffice Administration before use.

Activity & Appointment Macros

Deep links to onOffice-enterprise

Newsletter & Agreement

> 💡 Agreement link tip: Instead of fixed parameters in the email template, you can maintain a custom field in the property (e.g. agreement_link_parameter) and use a formula to dynamically supply different parameters there — e.g. no contract/cancellation for commission-free properties. The email template then only calls _AgreementLink(_agreement_link_parameter).

Address macro resolution mode “alternative”

In the propform email configuration, there is the setting “Address macro resolution: normal vs. alternative”:

When is it “alternative”? Whenever the email is sent to someone who is not the enquirer — e.g. an internal notification to accounts regarding a new address. Otherwise, accounts data would appear in the email instead of the enquirer’s data.

---

Loops — Search criteria loop

With _bScRek_ and _eScRek_, you can iterate through all search criteria for an address and output macros for each individual search criterion — similar to the familiar estate agent book loops in onOffice.

Syntax

_bScRek_("filter")
   ... beliebige Suchkriterien-Makros ...
_eScRek_

Optional filter

The filter argument allows you to restrict which search criteria are taken into account:

_bScRek_("status:1")

→ Active search criteria only (Status = 1).

Complete example

_bScRek_("status:1")
Objektart: _pfGetSearchCriteriaField(objektart)
Ort: _pfGetSearchCriteriaField(ort)
Wohnfläche: _pfGetSearchCriteriaField(wohnflaeche)
Link: _pfLink("https://example.com?id=_pfGetSearchCriteriaUUID", "Suchkriterium öffnen")
_eScRek_

Loops — Calendar Loop

_bCalendarRek_ and _eCalendarRek_ allow you to iterate through events in the specified time period — e.g. to display available slots in a booking form.

Syntax

_bCalendarRek_("startDate:YYYY-MM-DD;endDate:YYYY-MM-DD;weitere:filter")
   ... beliebige onOffice-Termin-Makros + _pfGetCalendarUUID ...
_eCalendarRek_

Example filter

_bCalendarRek_("startDate:2026-02-25;endDate:2026-12-31;subject:like:%TERMIN-SLOT%;estate.id:_Id")

→ All appointments within the period whose subject contains “APPOINTMENT-SLOT” and which are linked to the current property.

Dive deeper

You can find detailed instructions with copy/paste prompts on the blog: Calendar-Loop Filter Guide.

Loops — Address Loop (Buyers / Owners)

The address loop macros allow you to cycle through all buyers or owners associated with the property — a typical use case: an overview form listing all individuals associated with a property, plus ‘Edit’/‘Link more’ buttons.

Syntax

> Within the loop, you use the pre-macros _Buyer* and _Owner* (see next section). _1_ is an internal loop counter — only increment it if you need multiple independent buyer/owner loops within the same description field.

Example — listing all buyers of a property

_buyerbrek_1_
_BuyerVorname _BuyerName, _BuyerStrasse, _BuyerPLZ _BuyerOrt, _BuyerEmail
_buyererek_1_

📖 Full tutorial with overview + editing form and code examples: Linking multiple records with a form

---

Pre-macros (accessing linked records)

Pre-macros access address records that are linked to a property — typically within PDF templates, emails or address loops.

Pre-macros for buyers

Pre-macros for owners

> 💡 Buyer/Owner vs. Kaeufer/Eigent: _Buyer*/_Owner* are primarily used within address loops and in the description field. _Kaeufer*/_Eigent* (with German names) are the classic pre-macros from PDF templates that onOffice understands directly. For PDF templates → see Values are not transferred to the PDF.

Direct access to contact type links

Instead of cycling through all linked addresses for a property, you can also address a specific contact type directly — e.g. the solicitor or the property management for that property:

_XAPKontaktart#NAME#FELD

> 💡 Finding the key value: You can find the exact name of the contact type in onOffice under Tools → Settings → Administration → Addresses → ‘Contact type’ field → the key value is listed next to the respective option (often indXXXX).

Pre-loading UUIDs without a field in the form

Even if a form contains no address or property fields, you can “pass along” a record via a URL parameter — the activity created after submission is then linked to this record.

https://formular.deine-domain.de/dokumenten-upload?address[ID]=_Uuidaddress&estate[Id]=_Uuidestate

Use case: A document upload form for a tenant (address) that is still intended to retain a property reference — the uploaded file and the activity are then linked to both records, even if the form itself only contains file upload fields.

> 💡 Also works for _AgreementLink calls and all instances where propform expects UUID parameters.

Continue to Emojis & Symbols for onOffice 👉