Appearance
AbcSubmit terminology
Use this page when a guide and the editor use different words for the same concept.
| Term | Plain-language meaning |
|---|---|
| Form | The questions, instructions, layout, and submission rules shown to a respondent. |
| Field | One input or content element in a form, such as Email, Date, File Upload, or Text. |
| Field settings | Options that affect one selected field, including its label, required state, validation, and appearance. |
| Form settings | Rules that affect the whole form, such as security, notifications, submissions, and analytics. |
| Preview | A respondent-style view used to check layout and behaviour before publishing. |
| Submission | One completed response sent by a respondent. |
| Workflow | The process that runs after submission, such as notification, approval, or an external request. |
| Workflow node/block | One step in a workflow. The live palette may call Form Fill “Assign Form” and HTTP Request “Http Request.” |
| Condition | A rule that evaluates data and can show/hide fields or choose a workflow path. |
| Integration | A connection to an external service, such as Slack, Google Sheets, or a CRM. |
| Gateway | A payment-provider connection, such as Stripe or PayPal. |
| Quick share | A direct URL to the hosted form. |
| Embed | Code or a widget that displays the form inside another website. |
| Hosted domain | An AbcSubmit subdomain or approved custom domain where the form is published directly. |
| Test form | A non-production form used to safely test changes before applying them to a live form. |
How to read a guide
Where to find it tells you which navigation item to open. Configure describes the values to choose. Expected result tells you what a successful setup looks like. Safety or Important safeguards identifies actions that can send messages, charge money, expose data, or change a public form.