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

Add a Sign button for your experience

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.

The Sign button from Add the Sign button always shows the standard form. For a button that uses your experience, make a small Lightning component that holds the Experience ID. Then make an action from it. You copy the code from this guide.

  1. Open the Developer Console.

    Click the gear icon at the top right. Click Developer Console. It opens in a new window. If no window opens, allow pop-ups for Salesforce in your browser, and click Developer Console again.

  2. Click File, then New, then Lightning Component.

    In Name, type SignContact. Use letters only, with no spaces. Leave the boxes under Component Configuration as they are. Click Submit.

  3. Replace the code in the Component tab with this code.

    Select all the code in the tab and delete it. Then paste this code.

    <aura:component implements="force:appHostable,flexipage:availableForAllPageTypes,flexipage:availableForRecordHome,force:hasRecordId,forceCommunity:availableForAllPageTypes,force:lightningQuickAction" >
    	<aura:attribute name="recordId" type="String" /> 
    	<aura:attribute name="experienceId" type="String" default="XXXXXXXXXXXXXXX" /> 
    
        <div class="slds">
    
            <div class="slds-page-header" role="banner" id="mobHeader">
                <div width="100%">                     
                    <span><center><img src="{!$Resource.signature__SSLogo}"  style="height:25px;" /></center></span>
                    <span class="slds-text-heading--small"><center><b>{!$Label.signature.Page_Title}</b></center></span>
                </div>
            </div>
        </div>
    
        <signature:SignatureFormInfo experienceId="{!v.experienceId}" showLegalText="true"></signature:SignatureFormInfo>
    
        <!-- 
    
        	THIS CODE CAN BE USED TO INCLUDE A PDF ABOVE THE FIELDS
    	- MAKE UPDATES TO THE width, height, PDF_name
    	- CHANGE THE "Id" PARAMETER AS APPROPRIATE FOR THE PDF
    	- ADD THE NAME OF THE COMMUNITY NAME IF BEING USED IN A COMMUNITY, SUCH AS: /apex/community_name/PDF_name
    
        <iframe src="{! '/apex/PDF_name?isLight=yes&amp;Id=' + v.recordId }" width="100%"  frameBorder="0" height="500px"/> 
        <br />
    
        // -->
    
    	<signature:SignatureFormConnector recordId="{!v.recordId}" ExperienceID="{!v.experienceId}" isQuickAction="true"/>
    
        <div align="center" style="color:gray"><br/><br />Powered by <i><a href="http://www.simplesignatureapp.com/" target="_blank">Simple Signature</a></i> from To A Finish</div>
    </aura:component>
    

    The code is the file StandaloneSignatureForm-Simple.html in the lightning folder of the Simple Signature sample code on GitHub.

  4. Replace XXXXXXXXXXXXXXX with your Experience ID.

    It sits in the line that starts with <aura:attribute name="experienceId". Keep the quote marks. Put no space inside them.

    The Developer Console with the SignContact component. The Experience ID sits in the experienceId line.
  5. Save the component. Close the Developer Console.

    Press Ctrl+S on Windows or Command+S on a Mac. You can also click File, then Save.

  6. Rename the free Sign action.

    Open Setup. Click Object Manager. Click Contact. Click Buttons, Links, and Actions. Click the arrow at the end of the Sign row. Click Edit. Change Label to Sign (free). Click Save.

    The new button takes the label Sign. The old one leaves the page layout in step 8.

  7. Click New Action. Fill it in as below. Then click Save.

    FieldValue
    Action TypePick Lightning Component.
    Lightning ComponentPick c:SignContact, the component you made.
    HeightType 600px.
    LabelType Sign.
    NameSalesforce fills in Sign. Clear it and type Sign_Experience. The name Sign belongs to the free action.
    The New Action page for Contact with the component c:SignContact, height 600px, the label Sign and the name Sign_Experience.
  8. Swap the actions on the page layout.

    Open Page Layouts and the layout from step 4 of Add the Sign button. In the palette, click Mobile & Lightning Actions. Drag Sign (free) out of Salesforce Mobile and Lightning Experience Actions, back to the palette. Drag the new Sign into that section. Click Save.

  9. Take a test signature with the new button.

    Follow Take a test signature. The form now follows your experience.

    The form from the new Sign button: labels beside the fields, the Standard and Typed tabs, and the Sign Now button from the experience.

For developers

The same GitHub folder holds a Lightning web component version of this button, StandaloneSignatureFormLWC-Simple, and a full-screen form, Fullscreen_Component. Open a case if you want help with them.

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.