0.3.0
Released 15 August 2026, the first public release of Sliick Forms and where these release notes begin. Read the announcement.
The release where the admin surface became a product: the Admin Dashboard is the hub - search, folders, sort, New form, Import and Duplicate all live there - and the Form Builder is just the builder. Publishing a form now makes it live.
Building forms
Section titled “Building forms”- A drag-and-drop canvas, with drag-to-delete, per-field delete with undo, and a redesigned inspector.
- Pages have their own tab bar above the canvas. Every page can be named, given rules and duplicated, including the first.
- Name-first creation. Name the form and its external ID is derived from the name. A name already in use is refused clearly.
- Sections are real groups. A rule on a section hides everything inside it, and its fields are grouped visually using your own theme.
- Collapsible sections for longer forms. Collapsing is presentational only: answers are kept, rules keep working, and required fields still have to be completed.
- Repeating groups render columns, description text and hidden values in every row, and can be nested, with inner rows creating their records under the right parent.
- Record type mapping where a mapped object has more than one, required before publishing.
Respondents
Section titled “Respondents”- One public page can serve every form. Leave the component’s form ID blank and the page takes the form from the web address, so a single page covers your whole catalogue.
- A closed form says that it is closed.
- Answers a respondent could not see never reach your records, checked in Salesforce rather than relying on the browser, and rules that depend on each other now settle consistently.
Responses
Section titled “Responses”- A responses console you can work in. Open any response, see what processing would do before committing it, and correct answers in place. Corrections are stored alongside the response, so the original answers are never altered.
- Share links are resolved rather than guessed, using a per-form address or an org-wide template, and say so plainly when neither has been set.