0.6.0

Released 31 August 2026. Read the announcement.

Public hosting with Sliick Edge

• Publish forms on your own public web address. Connect your org to Sliick Edge from the Delivery panel on the Admin Dashboard and your forms can be served from an address of your own, without Experience Cloud.
• No form is public until you say so, form by form. Connecting the org publishes nothing on its own: each form has its own setting in the builder and in the publish dialog. A copy of a form never inherits it.
• Publishing confirms that your public address has the update, and says what to do if it does not. The first time a form is published on a connected org the setting starts switched on, and any later choice you make is remembered.
• Check whether a form is ready to serve, on demand, from the Share panel in the builder - including when a form is deliberately not being served.
• Starting or stopping an A/B experiment takes effect immediately on publicly hosted forms, rather than waiting for the next publish.
• Control which websites may embed a form, and which may read its data. The embed allowlist accepts exact addresses, and a separate list covers scripted access and allows a wildcard subdomain of your own domain. Leaving either empty keeps current behaviour.
• Copy a ready-made embed snippet from the builder’s Share tab once a form is eligible, with a clear explanation when it is not yet.
• Publicly hosted forms use signed requests, so only your own forms can submit to your address. Forms served through Experience Cloud or inside Salesforce are unaffected.

Admin dashboard and Sliick Responses

• Both pages have been redesigned. The forms list takes the main column, with search, filter, sort and its actions together in a sticky header, and the org’s delivery settings are gathered into one panel with a tab for each option - Sliick Edge, Experience Cloud and a custom site - each showing its own status.
• The Experience Cloud tab previews the actual link a form would be given as you type your address, so you can see it is right before saving.
• Sliick Responses shows the answers respondents actually gave. Filtered to one form, the list shows that form’s questions as columns; otherwise each row carries a short summary.
• Duplicating a form asks what to call the copy, prefilled with a suggested name.
• The survey pulse panel has been retired from Sliick Responses. The NPS starter, its score field, and those answers in results and exports are unchanged; a dedicated analytics page is where a roll-up will live.
• The getting-started steps match the redesigned dashboard, and point to where a published form’s public link is now shown.

Save and continue, and prefilled links

• Save and continue now works for long forms and across devices, keeping repeating rows, multiple file uploads and the respondent’s place in the form. Saved progress and its link last seven days, and administrators can clear them.
• A saved link stops working once it has been used to submit, so reopening it starts a fresh form rather than resending answers already received.
• Fields can be filled in from the page link. Switch on Accept a value from the page link for a field and a link carrying a value will seed it. It is off by default and never offered where it would be unsafe.
• A field can keep its own link parameter name, separate from its Salesforce name, so links already in circulation keep working after a field is renamed. This is currently set through a blueprint or the API rather than in the builder.
• Answers a respondent has already been given are no longer overwritten when a form opens on a record.
• A checkbox set to start ticked now recognises the common ways of writing that, not one exact word.

Building forms

• Multi-page forms can show each page’s name to respondents. Name a page in the builder and it appears as a heading above that page’s fields, and groups its answers on the review screen. Unnamed pages look exactly as before.
• The builder canvas matches what respondents see more closely, with tighter spacing, and an image block without a picture now shows a placeholder rather than an almost invisible card.
• Forms that map more than one object have a visible object model. The builder asks which relationship should join two objects as soon as that becomes ambiguous, and you can choose which object the form is primarily about.
• Publishing catches two setup problems earlier: fields that share a name, and forms with rules that loop.
• Text formatting settings now apply to published forms, not only to drafts, with no need to republish. The Trim Whitespace option has been removed, as Salesforce already does this.
• Theme colours accept a wider range of colour formats, and corner radius and field spacing are now guided controls with a live preview and a custom option.
• Creating a form from a starter is reliable when several people are creating forms at the same time.
• Fixed: a multi-select question with a preset answer could leave a form loading. It now renders normally everywhere.
• The Contact and Event registration starters collect first and last name separately, so names land in the right Salesforce fields.

Clearer messages

• Around two dozen messages now explain what happened and, where there is one, what to do about it, instead of a generic error.
• A correction that could not be applied is reported rather than quietly set aside.
• Comparing two published versions reports only real differences, and now includes changes to a field’s name and formatting.

Documentation

• A new uninstall guide covers what uninstalling removes, exporting your data first, and the order to reverse setup steps in.
• The developer reference documents the packaged integration app, what each route expects and returns, and a worked example.
• The delivery, results and object model sections of the admin guide have been rewritten to match the redesigned dashboard and console.