Under Settings → Templates → Dynamic Forms, you build structured forms that collect data in a guided way – from the client or internally. A form is designed once, centrally, and then used according to its type.
The three form types
The type determines where and how a form is used:
| Type | Internal | Use |
|---|---|---|
| Acquisition | ACQUISITION |
New-mandate intake: a prospect fills out the form, and DEPLAW creates a new case file from it. |
| Forward | FORWARD |
Sent to an existing client within a case file – see Forward Forms. The answers flow back into the case. |
| External | EXTERNAL |
A publicly embeddable form (e.g. on your website) that can be filled out without a client portal. |
The form designer
+ Create form opens the designer. Under Form settings, you set the title, slug, description, type, and size; then you drag building blocks from the Components palette onto the canvas:
The palette is organized into Input, Selection, and Presentation. Alongside standard fields (text, number, date, file), there are DEPLAW-specific building blocks:
- Beteiligter / Beteiligten Gruppe – collect entire contact records that get added directly as participants of the case file.
- Euro field – amounts; Date time – dates.
- Unterschrift – legally binding signature (e.g. for powers of attorney).
- Dokument Hochladen / Dokument Anzeigen – request files or display a document.
- Mollie Payment – collect a payment directly within the form.
- Anmeldemaske – client portal registration; Verstecktes Feld – pre-filled, invisible values; Have I Been Pwned – password check.
Multi-page forms
A form is organized into pages (sections) – on the right side of the designer, you see the page list (e.g. Intro, Claim 1, Opposing Party, Sign-up). Add creates a new page; each page has a gear icon for its settings. On the fill-in side, the presentation building block Continue moves the user from one page to the next.
Field properties
Clicking a field in the designer opens its properties panel on the right. It’s structured similarly for all field types:
The most important properties and what they do:
| Property | Function |
|---|---|
| Field label | the visible label of the field (also settable via FEEL ƒx). |
| Field description | explanatory hint text below the field. |
| Key | the variable name under which the answer is stored (“binds to a form variable”, e.g. ANSPRUCHSHOEHE_1). You reference the field by this key in conditions and as a placeholder. |
| Default value | the field’s pre-filled value (a literal value or FEEL). |
| Disabled / Read only | grays out the field or makes it read-only (Read only can also be driven by FEEL). |
| Condition → Hide if | a FEEL expression; if it evaluates to true, the field is hidden. |
| Layout → Columns | column width in the grid (Auto, 1, 2 …) for multi-column layouts. |
| Tooltip | an info icon on the field with a tooltip header + text (basic HTML) – guidance while filling out the form. |
| Validation | Required (mandatory field) as well as Minimum / Maximum (value limits, each settable via FEEL) – e.g. an amount between 25 and 250,000 €. |
| Custom properties | your own additional attributes for special cases. |
Form step settings
The gear icon on a page opens its form step settings. Here you control the entire page – most importantly, the condition that decides whether a page appears at all:
- Condition – a FEEL expression that decides whether the entire page is shown. It has access to the keys of earlier fields – e.g.
MEHRERE_FORDERUNGEN = "Ja"shows the page “2. Claim” only if “multiple claims” was previously selected. The expression does not need to start with=. - Disable “Back” button – grays out the Back button on this page.
- Skip on “Back” – skips the page when navigating backward (e.g. for pure interstitial pages).
- Hide “Next/Submit” button – hides the Next or Submit button (for instance, when some action already advances the step on its own).