Glossary
Short definitions of the words this documentation uses. Read this if a term in the product is not obvious.
| Term | What it means |
|---|---|
| Blueprint | The portable file for one form: its definition, its elements in order, and their configuration. Used to move a form between orgs |
| Champion and challenger | In an A/B experiment, the currently published version and the version being tested against it |
| CORS allowlist | The sites allowed to fetch a form’s data from their own script. Separate from the embed allowlist, and it does accept a single leading wildcard subdomain |
| Delivery panel | The Admin Dashboard panel holding the org’s three delivery options: Sliick Edge, Experience Cloud, and Custom site |
| Draft | The version of a form you are editing. It autosaves as you work and respondents never see it |
| Embed allowlist | The sites allowed to put a form in a frame. Exact addresses only, and a blank list permits nobody |
| External ID | The stable, environment-neutral key for a form. Every public link is built from it, and blueprint import and export depend on it. Fixed once the form is created |
| Form Builder | The editor for one form: palette, canvas, inspector, settings, publishing, versions |
| Form Definition | The form itself as a Salesforce record. Deleting it deletes the form |
| Integration user | The dedicated Salesforce user a connection signs in as, never a person. Used for Sliick Edge and for your own integrations |
| Mapping | The Salesforce object and field an answer is written to at processing. An unmapped answer is still captured, just not written |
| Match key | The mapped fields ticked with Use for matching. Together they decide whether a submission updates an existing record or creates a new one |
| Object model | For a form mapping more than one object: which object it is mostly about, and which lookup joins the records it creates |
| Person account | On orgs that use them, an account that represents a person. A form mapping onto Account there has to choose which kind it creates |
| Prefill link | A link that starts a respondent off with answers already filled in from a record |
| Processing | The step that maps a staged submission onto Salesforce records. Nothing is written to your records until it runs |
| Published version | An immutable snapshot of the draft, taken when you publish. It is what respondents are served |
| Repeating group | A block of fields a respondent can fill in more than once. Each row creates a child record |
| Response, submission | One respondent’s answers. It stages in the responses console as a submission record and is then processed onto records |
| Save-and-continue | The link a respondent uses to leave a form partway through and come back to it. Expires after 7 days |
| Sliick Edge | Our hosted option for public forms, serving them from a public address of your own with no Experience Cloud site required |
| Staged | Held in the responses console, received but not yet processed onto records |
| Starter | A ready-made form offered in New Form. It creates the fields and the layout, and no Salesforce mapping |
| Test respondent | A submission made with Open as test respondent. It does not count toward results, caps, or experiments, and is hidden in the console until you tick Include test |
| Visibility rule | The condition that decides whether a respondent sees a field, a section or a page |