Skip to content
SliickAll products
ServicesArticlesContact
Sliick Formsv0.6.0
Install free

Sharing a form

Once a form is published, the Share tab is where you get the link to hand out. With nothing selected on the canvas, open Share on the right rail.

Section titled “How the link is resolved”

The link is resolved, never guessed, in this order, stopping at the first hit:

  1. The form’s own Share URL, from Form settings, Availability. Paste the address where you actually placed the form. This is the answer for a form on a hand-built Experience Cloud page, embedded on a customer’s own site, or anywhere else only you know about.
  2. Your public Sliick Edge address, for a form with Allow on your public Sliick Edge address ticked. This one is delivered to the org when you connect Sliick Edge, which is why it outranks the template below.
  3. The org-wide Experience Cloud address from the Admin Dashboard’s Delivery panel, used as a template, with {form} replaced by this form’s external ID.
  4. Nothing.
Section titled “What you get when a link resolves”

The URL plus Copy link, Show QR, Download blueprint, and Open as test respondent, which fills in the live form without counting toward results, caps, or experiments.

When nothing resolves

Section titled “When nothing resolves”

The panel says so and offers Download blueprint and nothing else: no link, no QR code.

This is intentional. A form can be placed anywhere, so there is no address the org can derive for every case, and showing an incorrect link is worse than showing none. That is particularly true of a QR code, which is often printed before anyone tests it.

If you expected a link, check Choosing how to host a form: either the form needs its own Share URL, or the org needs an address set in the Delivery panel.

Section titled “Prefill links”

Prefill links start a respondent off with answers already filled in from a record. Pick the record by searching for it by name: the search is scoped to the objects the form maps to, so you do not need to paste a record ID.

A form that maps no fields says so rather than offering a picker that could not work, and a form that has not been published yet tells you to publish it first, because a prefill link against an unpublished form returns nothing.

Three things decide whether a prefill link fills anything in:

  • It is tied to one form and expires after 7 days. An expired link, or one made for a different form, is skipped quietly rather than failing.
  • Only mapped fields can be prefilled, because prefill reads the record through each field’s mapping.
  • On a form placed inside Salesforce, the person viewing needs read access to the record and its fields. Record-driven prefill is for placements where the respondent is signed in, not for anonymous visitors.

Values from the page link

Section titled “Values from the page link”

A field can also be filled in straight from the link’s own URL, separate from a signed prefill link: tick Accept a value from the page link on the field, and a URL such as ?utm_source=partner-x seeds it.

This is off by default, set per field, and never offered on a field used for matching, so a link cannot steer which record a submission updates. A signed prefill link always takes priority over it.

A field can also carry its own parameter name, separate from its API name, so a link already in circulation keeps working even if the field is later renamed. Setting a different name is not something the builder does today: it arrives with an imported blueprint. Publishing refuses two fields that would answer the same parameter, and a parameter name the form runtime already uses for something else.