What Sliick Forms is
Start here if Sliick Forms is new to you. This page explains what the product does and names the four pieces you will meet everywhere else.
Sliick Forms is a native Salesforce form engine. Admins build a form in a drag-and-drop builder, map each field to an object and field, and publish it. Respondents fill it in behind portal login on Experience Cloud, or in the open, on an Experience Cloud page or your own public Sliick Edge address.
There is no middleware to reconcile and no export and re-import. Every submission stages inside your org first, so you can review what it will write before it writes it, and processing then lands the answers on the right Salesforce records. A form on your Sliick Edge address reaches your org through hosting infrastructure we operate; every other placement talks to Salesforce directly.
The four pieces
Section titled “The four pieces”| Piece | What it does |
|---|---|
| Form Definition | The form itself, identified by a stable External ID that every public link is built from |
| Form Builder | Where one form is authored: fields, logic, pages, mapping, settings, publishing |
| Published version | An immutable snapshot of the draft, taken when you publish. It is what respondents actually see |
| Submission | A staged record of one respondent’s answers, which is then processed onto your Salesforce records |
Two distinctions worth understanding
Section titled “Two distinctions worth understanding”A draft is not a published version. Editing a form never changes what respondents are filling in at the time. Publishing is the separate step that makes your work live, and every version you have published stays available to compare against or restore from.
A submission is not the records it creates. Answers land in the org as a staged submission first, and appear in the responses console. Nothing is written to your Contacts, Cases or Leads until you process the submission, and you can preview exactly what processing will do before you run it.
Note: answers never write straight onto a target record. Staging first is what lets you review, correct and retry a response before it touches your data. See Processing responses onto records.