0.8.0

Released 20 September 2026. Read the announcement.

The theme of this release is getting a form to the right person already filled in, and letting them finish it later without losing anything or spending a response twice.

Record links

• Generate a personalised link from any record, from the record page, from Flow, or from Apex. It opens the form already filled in from that record’s values, expires in 7 days, stops working once the form is submitted, and generating it again replaces the previous one. The values travel as a signed reference rather than in the link itself. See Record links.
• See what the link will carry before you create it. Pick the form from a list filtered to the forms that map this record’s object, then see each field’s value read from the record, which field identifies it, and which are empty on the record. One click still creates the link.
• Add a one-off typed value for any field, mapped or not, from a drawer. It applies to that link alone and nothing is written back to the record. The field that identifies the record cannot be overridden.
• A question can be held back from every link. Tick Never prefill this field and that question is left out of record-driven prefill everywhere, without affecting save-and-continue.
• Flow and Apex accept the same per-link typed values. The invocable Create Sliick Form Record Link and FormsApi.invoke('createRecordLink', ...) take a value for an element and it replaces what the record would supply, or fills in an element the record does not map. See the developer reference.

Access

• Staff can be given the responses console without the form builder. Assign the new Sliick Forms Operator permission set and they can search responses, inspect the dry run, correct answers, process and retry, export the CSV, see the results and funnel panels, and generate record links, but they cannot create, edit, publish or delete a form. See Install and permission sets.
• Read this before assigning it. Working responses needs broad access to them: Salesforce only lets someone edit a record they do not own under Modify All, and Modify All cannot be granted without Delete. An Operator can therefore read, correct, process and delete every staged response in the org. Assign it to people you would trust with the responses themselves. Sliick Forms User stays read-only with no console.

Save and continue

• Save and continue later opens its own page, carrying the link, a Copy button and a Back to the form button that returns the respondent to their answers. The form and its Submit button are off screen for the whole save, on every surface the form is served from. See Save-and-continue.
• The Save and Submit buttons can no longer race each other on either surface: each is unavailable while the other is going through, so a response cannot be sent, or a saved link quietly overwritten, by one click at the wrong moment.
• Saving again updates the link the respondent already has instead of minting a second one, and submitting spends every copy of it.
• Reopening a saved link says “We restored your saved answers”, and the Start over button is gone. To begin a fresh response, open the form without the link.
• A spent link says the answers arrived, rather than claiming to have expired and inviting the respondent to fill the form in again.
• A form opened with a saved link always reaches a definite answer, within about eight seconds, instead of sitting on “Restoring your saved answers”. Answering while it is still loading now says restoring has stopped.
• The expired-link notice can be dismissed and clears by itself at the next page or the review screen.
• Submitting immediately after saving reliably spends the link. Pressing Submit a second or two after saving used to leave a link that reopened showing every answer on a form that looked unsubmitted, and submitting again consumed a second response against the form’s cap.
• Reopening after submitting no longer stages the response twice, Submit another response starts completely fresh, and a link that arrived complete no longer submits the form by itself on reopen.

Building forms

• Display Text blocks hold long-form content and support richer Markdown: paragraphs, bullet and numbered lists, headings, and email links alongside bold, italics and web links. Long privacy notices and GDPR disclaimers, with links to your policy page and a contact address, can go directly on a form, and the builder previews the formatting as you write. See Field types.
• Content too long to save is refused with an explanation, rather than a raw Salesforce error with your own text quoted back, and exports no longer include empty columns for headings, paragraphs, images and other blocks respondents never answer.
• Rounded corners and Space between fields are chosen by name - Square, Subtle, Rounded, Very rounded, Pill, and Compact, Comfortable, Roomy - instead of a measurement, with a custom length still available. Forms also draw a subtle outline, and the corner setting now shapes the answer boxes too, so it has a visible effect on every form rather than only those using Sections or Repeat Groups. See Themes and branding.

Publishing

• Publishing a form for the first time is one screen instead of a five-step walk: the message respondents see, when the form accepts answers, how records will link, and whether the form is served at your public address, each readable without opening it, with a checklist that clears as you answer. Republishing is unchanged, with an option to review those settings. See Publishing a form.
• A permission set that stops you editing one setting no longer decides the public address for you. The consent tick stays readable and editable, and a stored “Don’t link these records” is no longer repeated back as a publish warning.
• Fields can no longer be named after a link parameter the public form reserves. Three such names were missing from the check, so an admin could create a field that silently never filled from the link.

Fixes

• An admin whose permission set predates a packaged field can open the Form Builder again. The whole settings load used to fail, so the object-model section vanished and the public-address box showed unticked over a stored setting of on. The builder now loads every column that admin can read and names the ones it cannot, with the remedy.
• Processing no longer reports success for a result it could not record. Where the person processing can create the target records but cannot write to the response itself, the records were created while the response stayed on Received with no note of what it made, so the console offered to process it again and doing so created the records a second time. The run summary now names every response it could not record and the records each one created. Reachable only where a permission set or profile grants Edit on responses without Modify All; Sliick Forms Admin and Sliick Forms Operator were never affected.
• The builder no longer offers to restore unsaved edits left behind before someone else changed the same form, which would have deleted questions added in the meantime, and the recovery banner now shows a date.
• Preview asks before showing you a stale form, offering to save first or to preview the last saved version, and never discarding what is on the canvas.
• A Display Text block written before this release can be cleared, and the builder’s breadcrumb no longer repeats a whole paragraph.
• The Generate Link panel says “No forms available” when no form is set up for that record’s object.

Upgrading

Upgrade from 0.7.0.

If your admins hold a permission set you created yourself rather than the packaged Sliick Forms Admin, add two grants:

• Read and Edit on Form Element, Content, the new long-form Display Text field. Without it, the Form settings object-model section and the public-address tick can read wrongly for those admins.
• Read, Create and Edit on Form Partial, which is where a record link stores the values it will prefill.

The packaged permission sets are updated automatically, which is the reason to assign them rather than clone them. Sliick Forms Operator is new in this release and, like every packaged set, is assigned by you rather than automatically.

Every form gains a faint outline in this release, and its inputs take the theme’s corner radius, including forms whose author never opened the theme panel. See Upgrading the package.