Skip to content
New to Superprocess? The guided invoice walkthrough takes you from a blank canvas to a running workflow.Get started

Build a form

Forms are reusable, versioned building blocks. You design one in the Forms library at the organization level, then bind it to a user task.

  1. Create the form. Go to Forms (in the organization sidebar) and click New Form. Give it a name, keep the visibility as Organization, and the Designer opens.

    The form builder: the Add Field palette on the left (Basic, Choice, Date, Advanced, Layout), the design canvas in the middle, and a field editor on the right
    The form builder — add fields from the palette, edit each one, and preview.
  2. Add fields. From the Add Field palette, drop in the inputs you need:

    • Basic — Text, Long text, Number, Integer, Boolean, Email, URL.
    • Choice — Select, Radio, Multi-select, Checkbox group (each with a list of options).
    • Date — Date, Time, Date + time, Date range.
    • Advanced — File uploads, and Array (a repeating group of sub-fields — line items and the like).
    • Layout — Section, to group fields under a heading.
  3. Configure each field. Select a field to set its name, label, help text, and whether it’s required, plus any validation (min/max length or value, a pattern, min/max items, accepted file types).

  4. Add dynamic behaviour (optional). A field can show only when a condition holds, become required conditionally, compute its own value, or validate itself — expressed in FEEL. For an Array field, allow row editing so people can add and remove rows (bounded by a min and max).

  5. Define the actions. Set the buttons the person will see when completing the task — each has a label and a style (primary / secondary / destructive) and can require confirmation. These become the task’s completion actions (Approve, Reject, Request info…).

  6. Preview. Switch to the Preview tab and fill the form as an end user would, to check the validation and conditional logic behave.

  7. Publish a version. Click Publish version — pick a version bump and note what changed. A process binds a published version, so your edits don’t change a live task until you publish again.