A form opens in Studio › Forms › the form’s row. A user with the “Manage Studio” permission creates forms. The examples use the forms “Demo: Submit a shipment request” and “Demo: Request from a customer”.
Header
Status
“Draft v1” until the first publish, then “Published v1”. The number grows with each publish.
Copy link
Copies the link to the form; it appears after the first publish. See Share a form and review submissions.
History
The “Version history” of the form: every version with “Published”, “Draft” or “Archived”.
Save draft and Publish
Save draft keeps your changes without touching the form people fill in. Publish turns the draft into a new version. Submissions already started stay on the version they began with; new ones get the new version.
Key
The form’s code: lowercase letters, digits and dashes. It fills in from the name; to change it, edit it and click Apply.
Tabs
Builder
The steps of the form, in order. Add step adds one at the bottom; the arrows in a step header move it, the chevron opens its settings, the bin deletes it.
Intro page and Completion
The “Title” and “Description” the person sees before the first step and after the last one. The description takes Markdown; Preview shows how it looks.
Submissions
Who filled in the form, the “Status” and when it was updated. Filter with “All”, “Completed” and “In progress”.
Step settings
Filled by
- “Owner” — someone in your account.
- “Counterparty” — a person from another company who opened your link.
Each step is filled by its own side, in the order of the steps. See Collect a request from a customer and finish it in your team.
Title
The name of the step in the form’s progress bar. Required.
Entity type
What the step fills in:
| Entity type | What the person does |
|---|---|
| “Data model” | Fills in the fields you checked; the step creates a record in the model you select in “Data model” |
| “Truck”, “Trailer”, “Driver”, “Company” | Works with their own list of trucks, trailers, drivers or companies: adds, changes and removes entries, then clicks Next |
| “Brand” | Fills in the brand profile: name, color, about, website and logo |
Fields
For a data model, check the fields the step shows. A field is required in the form when it is marked Required in the data model. A relation is not a field of a form: link records with Add link.
Records required
For “Truck”, “Trailer”, “Driver” and “Company”, turn on Records required: Next stays off until the list has at least one entry, with “Add at least one record to continue”.
Reuse an earlier step's record
The step completes the record of an earlier step instead of creating a new one. Select that step in “Reuse record from step”: only earlier steps of the same type are listed.
Allow multiple records
The person enters several records in one step, for example several cargo items: Add record and Remove record under the fields. “Min records” is at least 1; leave “Max records (optional)” empty for no upper limit. A step with several records cannot reuse a record or have links.
Links
Add link connects the record of this step to the record of an earlier step: “Link type” is “Data relation”, then choose the “Relationship” between the two data models and the “Target step”. Both steps must fill data models.
Submission statuses
| Status | Means |
|---|---|
| “In progress” | Someone is filling in the steps, or the next step waits for its side |
| “Processing” | A workflow checks the step; the person sees “Processing…” |
| “Completed” | All steps are sent |
| “Rejected” | Someone in your account cancelled the submission with Cancel |
A sent step cannot be changed.
Checking a step with a workflow
A workflow with the “Forms” source starts when a step is sent. With “Wait for the workflow before advancing the form” on, the form waits for it: the submission is “Processing” until the workflow accepts or rejects the step. A rejected step opens again with the workflow’s messages. Only one workflow can make a step wait. See Check a form step with a workflow.