Make a PDF page in Visualforce

Last updated 9 Oct 2026

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

Use a Visualforce page if you do not use Google Docs. Most Visualforce pages need a developer, because each design is different. TAF builds pages at its hourly rate. Email [email protected].

The pages folder of the sample code on GitHub holds these pages to start from, among others. Their file names end in .html, but they hold Visualforce code.

1. Open Visualforce Pages. Click New.

   Open Setup. In the Quick Find box, type Visualforce Pages. Click Visualforce Pages. If you see no New button, ask your admin for the right to make pages.

2. Type a Label and a Name. Delete the code in the page.

   For example, Label Signature PDF and Name Signature_PDF. The Name can fill in by itself, with spaces. A Name takes no spaces, so type an underscore in place of each one.

3. Paste the code of a sample page. Click Save.

   On GitHub, open the page in the pages folder, for example SamplePDF_v2. Click Raw to see the code without the line numbers. Copy all the code, from <apex:page to </apex:page>. Paste it into Visualforce Markup.

4. Give the profiles access to the page.

   In the list of Visualforce pages, click Security beside the new page. Add all the profiles, or at least the profiles of the users who work with Simple Signature. Click Save.

5. Make Simple Signature use the page.

   Use the page name with c__ in front, for example c__Signature_PDF. Without c__, Simple Signature cannot find the page.

   For	Where to put it
   All signatures	Template VisualForce Page for PDF on the Configuration tab. See step 4 of Connect the site.
   One experience	The parameter pdftemplate. See Document parameters for an experience.
   One request action	A predefined value for PDF Template, in quote marks.

6. Send a test request. Open the signed PDF.

   Follow steps 6 to 9 of Send a signature request. The signed PDF in Notes & Attachments of the Signature now uses your page.

   If no signed PDF comes, see The signer signed, but no PDF comes.

   

The Opportunity and Quote samples

These two samples need an Apex class, so make them in a sandbox and deploy them to production. Production does not let you write Apex directly.

• Open Setup. In the Quick Find box, type Static Resources. Click New. Name it sampleinvoice. Pick the file SampleInvoice.zip from the resources folder on GitHub. Set Cache Control to Public. Click Save.
• Open Apex Classes. Click New. Paste the code of SampleOpportunityPDFController or SampleQuotePDFController from the classes folder on GitHub. Click Save.
• Make one more class with the matching test class from the same folder. Salesforce needs it for the deploy to production.
• Make the page as in steps 1 to 5 above, with the code of SampleOpportunityPDF or SampleQuotePDF.

Other document apps

Simple Signature can also work with a document app such as Salesforce CPQ, S-Docs, Conga Composer or Nintex DocGen. This way needs a lot of technical work, so TAF advises Google Docs. Open a case if you need help.

If the app reads values from one object only, copy the signature to that object:

• On that object, make a Rich Text Area field SignatureImage__c and a checkbox field Signed__c.
• On ß Signature, make a lookup field to that object, if none exists.
• Build a Flow on ß Signature. When the Status changes to Signed, copy the Signature field, and the Date field if you need it, to the object.
• Put the new image field into the template of your document app.

A person who knows your document app then does the rest:

• Build a trigger that makes a Signature request from each new document. Start from CreateSignatureOnAttachments or CreateSignatureOnFile in the triggers folder on GitHub. Both expect a parent object named Quote__c. Change it to yours.
• When the Signature is Signed, make the document again, with a Flow or a trigger. The new document holds the signature.

Was this helpful?

Yes No

Related

• All Simple Signature how-to articles
• Simple Signature troubleshooting