Upgrading the package

Upgrading is installing the new version over the old one, in the same org and the same way you installed it. Upgrades preserve your forms, your responses and your permission-set assignments. This page is the short list of what to confirm afterwards.

After upgrading, re-check

1. Permission-set assignments survived and the admin app still opens. Open the App Launcher, open Sliick Forms Admin, and confirm all four tabs load.
2. Any new fields the release added are visible to the site’s guest user, if you serve public forms on Experience Cloud. Field visibility lives on your own guest profile, so the package cannot manage it: a release that adds a field the public form reads needs that field made visible by hand. This is the classic post-upgrade failure, and it shows up as a form that renders with pieces missing rather than as an obvious error. See Guest access for public forms.
3. A public form still loads and submits. Open it in a private browser window, with no Salesforce session, submit it, and confirm the response appears in Sliick Responses.
4. Existing forms still serve their published version.

Assign packaged permission sets rather than copies of them. An upgrade updates a packaged permission set in place and can never add a new grant to a copy you own, so a clone falls behind quietly and fails later on something that used to work.

What v0.9 needs from you

The packaged permission sets update themselves. Everything below is yours to do. The 0.9.0 release notes list what changed.

• A guest profile you configured yourself: grant Read on the form’s Language and Translations fields, or a closed form shows in English.
• A permission set you wrote yourself: Read on Form Submission’s Suspected Duplicate and Answers Digest for any identity you gave Create, and Read on Failed Validation and Validation Errors for identities that process responses.
• API Enabled for the integration user. A packaged set cannot deliver it.
• Webhook hosts must be in Remote Site Settings, or deliveries fail silently.
• Republish forms that map number, currency or rating questions to number fields, and 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

The packaged sets are updated for you. If your admins hold a set you created, add:

• Read and Edit on Form Element -> Content, the long-form Display Text field. Without it, the Form settings object-model section and the Sliick Edge consent tick can read wrongly for those admins. A builder that cannot read a packaged column now names the columns it could not read, with the remedy, rather than failing the whole settings load.
• Read, Create and Edit on Form Partial, which is where a record link stores the values it will prefill.

Sliick Forms Operator is new in v0.8. Nothing is assigned automatically, so assign it to the staff who work responses without authoring forms. See Install and permission sets.

One visual change reaches every form in v0.8: a subtle outline around the form, and the theme’s corner radius on the answer boxes, including on forms whose author never opened the theme panel.

The release notes for each version call out anything upgrade-sensitive, including new fields a public form reads. See Sliick Forms releases.