Skip to content
Book a Demo Open a Case

Salesforce apps by To A Finish

Four managed packages that run inside your own Salesforce org.

Simple Signature

Document creation and e-signatures in Salesforce

Address Verification

Clean, verify and geocode Salesforce addresses

Highlighter

Colors, renames or hides Salesforce fields

List Browse

Browse Salesforce records without list clicking

Get started

Install, configure and roll out a TAF package.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article per task

Book a demo

See a package in a live org

Compatibility

Editions and releases we support

Get help

Open a case and a person reads it.

Open a support case

The fastest route to an answer

Give us access

Let us sign in and see the problem

Support home

Guides, release notes and the case form

Troubleshooting

Search by the error text you see

Documentation

Written for admins, not for developers.

Implementation guides

Guides for all four apps are ready.

How-to articles

One task per article

Change log

What changed in each release

Compatibility

Editions and seasonal releases

Simple Signature Address Verification Highlighter List Browse Support Book a Demo
Simple Signature · How-to

Advanced form options

How to do it in Simple Signature, one step at a time.

Last updated 9 Oct 2026

Paid version only. These steps do not count in the setup progress.

These options serve special cases. Most orgs do not need them.

Different legal text for one form

The labels from Set the wording of the form give every form the same title and legal text. A form type gives one experience its own legal text.

  1. Add the parameter formtype to the experience.

    On the Experiences tab, open the experience and click Edit. Click Add Advanced Parameter. Pick formtype. In Hardcoded Value/Field Reference, type a name for the form type, for example Visitor_Release. Click Save.

  2. Open Custom Metadata Types. Click Manage Records beside ß Form Type.

    Open Setup. In the Quick Find box, type Custom Metadata Types. Click Custom Metadata Types.

  3. Click New. Fill in the record. Then click Save.

    Type the Label first. Salesforce fills in ß Form Type Name from it. Then change ß Form Type Name to the formtype value.

    FieldValue
    LabelA name for the record, for example Visitor Release.
    ß Form Type NameThe same name as the formtype value, for example Visitor_Release.
    Legal TextThe legal text for this form.
    Signature URLLeave it blank. It serves signature requests.
    Thank You URLLeave it blank. It serves signature requests.
    Other fieldsLeave them blank.

    If the page does not show all these fields, save the record. Click Edit Layout at the top right, add the fields, and edit the record again.

  4. Take a test signature.

    The form shows the legal text of the form type. The title stays as Page_Title sets it.

Longer field labels

A Salesforce field label holds up to 40 characters. The ß Custom Labels setting gives a field on the form a label of up to 255 characters. The longer label shows on every Simple Signature form.

  1. Open Custom Settings. Click Manage beside ß Custom Labels.

    Open Setup. In the Quick Find box, type Custom Settings. Click Custom Settings.

  2. Click New. Fill in the record. Then click Save.

    FieldValue
    NameAny name that no other record in this list uses.
    API NameThe API name of the field on the form, for example signature__Company__c.
    Language CodeThe language of the form, for example en for English.
    LabelThe longer label, up to 255 characters.
  3. Add the parameter language to the experience.

    Give it the same code as the record, for example en. Then take a test signature.

Update the parent record after a signature

To change the parent record when someone signs, build a record-triggered Flow on ß Signature. Start it when the Status changes to Signed. For example, the Flow can move an Opportunity to its next Stage.

For values that are not on the form, Simple Signature has the ß Field Updates setting. Code writes a ß Field Updates record before the form opens. When the signer signs, Simple Signature copies the value to the parent record. When the signer cancels, Simple Signature deletes the record. A developer sets this up from the FieldUpdates class in the classes folder of the sample code on GitHub.

Applies to

Simple Signature 5.8.x, paid version. These steps come from the tested Simple Signature implementation guide, where they sit with the steps before and after them.

Was this helpful?

Related

Support

Still stuck?

Open a case and paste the exact error text. A person reads every case.