Upgrading the package
To upgrade, install the new version over the old one, in the same org and the same way you first installed it. Your forms, responses and permission set assignments are kept.
After upgrading, check
Section titled “After upgrading, check”- The admin app still opens. In the App Launcher, open Sliick Forms Admin and check all its tabs load.
- The site’s guest user can see any new fields, if you serve public forms on Experience Cloud. The package cannot change your guest profile for you. If a release adds a field the public form reads, make it visible by hand. When this is missed, the form usually loads with pieces missing rather than showing an error. See Guest access for public forms.
- A public form still loads and submits. Open it in a private browser window (not logged in to Salesforce), submit it, and check the response appears in Sliick Responses.
- Existing forms still show their published version.
Assign the Sliick Forms permission sets, not copies of them. An upgrade updates the packaged permission sets for you, but never your copies. A copy falls behind without warning, and later something that used to work stops working.
What v1.3 needs from you
Section titled “What v1.3 needs from you”Nothing. 1.3 adds no fields, so you do not need to change any guest profile or permission set. The 1.3.0 release notes list what changed.
- Web fonts need no set-up on Experience Cloud: the site’s guest user can already load them.
- A/B tests running during the upgrade keep each respondent on the version they already have.
What v1.2 needs from you
Section titled “What v1.2 needs from you”Nothing, for most orgs. The Sliick Forms permission sets update themselves, and nothing needs adding to your guest profile. The 1.2.0 release notes list what changed.
- A permission set you made yourself: give your form authors Read and Edit on the Form Definition field Sliick Edge Address. Without it, new forms are created without a Sliick Edge address and the address cannot be changed in Form settings. See Each form’s Sliick Edge address.
- A Source Channel you set on the Sliick Experience Form component is no longer used. A rule that tests the channel on that page now reads
experience. Check any rule that relied on your own value. - Record links work once. After a response is submitted through one, it shows This link has already been used. If a Flow or process sends the same record link more than once, create a new link each time. See Record links.
- Unsent answers on a device are cleared once. On an Experience Cloud or Lightning page, answers a respondent typed but had not sent or saved are cleared the first time that form opens on that device after the upgrade. Saved links are not affected.
- Existing forms keep their links. They get no Sliick Edge address until you set one.
What v1.1 needs from you
Section titled “What v1.1 needs from you”Nothing, for most orgs. 1.1 adds no fields, so you do not need to change any guest profile or permission set. The 1.1.0 release notes list what changed.
- If your org first installed a version before 1.0, the Admin Dashboard shows a notice. Click Finish upgrade steps to add the Column value. You need the packaged Sliick Forms Admin permission set (a copy made before 1.1 is missing what this step needs) and the Customize Application permission. See The Admin Dashboard.
- Nested layouts show on Experience Cloud and on forms hosted on Sliick Edge. The mobile app does not support them yet, so it shows a notice instead of a form that uses one.
What v1.0 needs from you
Section titled “What v1.0 needs from you”The Sliick Forms permission sets update themselves. The 1.0.0 release notes list what changed.
- Add the Column value once, if your org had Sliick Forms before 1.0. Until you do, a Columns block cannot be saved. Either:
- from 1.1, click Finish upgrade steps on the Admin Dashboard, or
- add it by hand: Object Manager, Form Element, Fields & Relationships, Type, New, value
Column.
- Open each form built before 1.0 in the builder and choose Upgrade. Published forms keep working as before until you do. A form that is switched on but was never published is not shown to respondents until it is saved.
- Download blueprints again from the upgraded org. Blueprints exported before 1.0 cannot be imported.
- A version published before 1.0 is still served, but cannot be restored. If a form that was switched on but never published had responses fail, save the form, then use Retry on them.
What v0.9 needs from you
Section titled “What v0.9 needs from you”The Sliick Forms permission sets update themselves. The rest is up to you. The 0.9.0 release notes list what changed.
- A guest profile you set up yourself: give Read access to the Form Definition fields Form language and Translations JSON, or a closed form shows in English.
- A permission set you made yourself: on Form Submission, give Read on Suspected Duplicate and Answers Digest to anyone with Create, and Read on Failed Validation and Validation Errors to anyone who processes responses.
- The integration user needs API Enabled. The packaged permission set cannot give this.
- Webhook addresses must be in Remote Site Settings, or webhooks stop arriving without any warning.
- Republish forms that map number, currency or rating questions to number fields. Rename any visibility-rule field whose name uses non-English characters.
- Schedule the clean-up flows if you want them. Nothing is deleted until you do. See Scheduled clean-up.
What v0.8 needs on a permission set you wrote yourself
Section titled “What v0.8 needs on a permission set you wrote yourself”The packaged permission sets are updated for you. If your admins use a permission set you made, add:
- Read and Edit on Form Element’s Content field (the long text of a Display Text block). Without it, some form settings and the Sliick Edge consent tick can show wrongly for those admins. The builder names any field it could not read.
- Read, Create and Edit on Form Partial. A record link stores its prefilled values there.
Sliick Forms Operator is new in v0.8. Nobody gets it automatically. Assign it to staff who work on responses but do not build forms. See Install and permission sets.
One visual change reaches every form in v0.8: a light outline around the form, and the theme’s corner rounding on answer boxes, even on forms whose theme was never changed.
What v0.4 needs from you
Section titled “What v0.4 needs from you”- Review the guest user’s permissions on any public site. See Guest access for public forms.
- Publish any form that is switched on but has never been published, or switch it off. A form accepts responses only once it is published.
The release notes for each version point out anything that needs attention when upgrading, including new fields a public form reads. See Sliick Forms releases.