Inline form

An inline form is embedded directly in your page's own layout, like any other piece of content on the page — it's not a modal, and it doesn't float above anything. It's simply part of the page, visible to every visitor who scrolls to it, with nothing to click to open it.

Use cases

An always-visible feedback prompt anchored to one key page (checkout confirmation, your dashboard, a docs article) — feels like part of the page rather than an interruption.
Long-form content (articles, documentation) where readers can leave feedback whenever they want, at their own pace, without a popup breaking their flow.
Revealed only after a specific moment: inline forms support the same delay/click-trigger settings as popups (see Settings), so you can have one fade in only after a visitor scrolls to it or clicks something — without ever using a modal.

Configuration

Same step/field editor as every other type — add steps and fields from the survey editor, see Field types and Steps. Inline forms don't have any type-specific settings beyond that (no trigger button, no delay/trigger config — those only apply to popup forms, see Settings).

Printing and PDF

An inline form can be printed as an ordinary questionnaire — to hand out at an event, leave on a reception desk, or collect answers somewhere without internet. There are two ways to open the print window:

in the survey list — the printer icon in the survey's row (the Print column);
in the survey editor — Actions → Print or save as PDF.

In the window, choose how the page will look:

Language — one of the domain's languages. Both the survey's own text and the answering hints print in it.
Paper size — A4 or Letter, and Orientation — portrait or landscape.
On the page — the survey title, the welcome screen text (if it's enabled), question numbers, answering hints ("Choose one answer", "Choose all that apply" and so on), the survey theme colors, and starting each step on a new page.

Print opens the browser's print window. Download PDF opens the same window — pick "Save as PDF" as the printer there, and the file is saved under the survey's name.

On paper every question gets a place to answer: circles where one option is needed, squares where several can be chosen, lines for text, boxes for dates, scales with marks and grids for matrices. A Rank order question prints as a grid of places: one place is marked in each row, and each place is used only once. With more than ten options, the place number is written next to each option instead. Required questions carry an asterisk. Conditional labels print their default wording — on paper there is no earlier answer for them to depend on. Links in text blocks, sections and consent boxes print with their address after the text, for example "privacy policy (example.com/privacy)".

With Survey theme colors ticked, circles, squares, stars and scales print in the color from the survey's theme, or in a field's own color variant where it has one. Text stays black. A color too pale to show up, a yellow for instance, prints darker so the marks stay visible on paper and on a black-and-white printer. Without the option the whole page prints in black and white.

The editor prints the survey exactly as it is open right now, unsaved changes included, so a draft can be printed before it's published. The survey list prints the last saved version. Answers filled in on paper don't reach Oiva by themselves.

Printing is available for inline forms and on-site surveys; popup forms don't have it.

Publishing requirements

Publishing enforces the same baseline as every type: at least one step, at least one field per step, and every translated field/label filled in for each of the domain's locales.

One field should be flagged as the main evaluation question, and one as the main feedback text (used elsewhere in the app — see Responses — as the response's headline score and quoted comment). For an inline form, missing either one is only a non-blocking warning: the editor will nudge you, but you can still publish without them. Popup forms enforce both as hard errors instead — see Popup form.