Any developer knows that VisualForce pages can be rendered as PDF. Using VisualForce to generate PDF documents is cumbersome, has many limitations in the PDF look&feel, time to market and maintainability.
To use a PDF generated by VisualForce, the PDF will require sign placeholders. You can download them here: Sign placeholders on the Academy
See an example of a VisualForce page that has 2 signers (a static resource is used that has the sign placeholder images as downloaded from the link above):
<apex:page showChat=”false” showHeader=”false” applyBodyTag=”false” applyHtmlTag=”false” renderAs=”PDF”>
<html>
<body>
<table width=”100%”>
<tr>
<td width=”50%”>Signer 1</td>
<td width=”50%”>Signer 2</td>
</tr>
<tr>
<td><apex:image url=”{!URLFOR($Resource.SIG001TOSIG010, ‘SIG001.png’)}” alt=”SIG001″/></td>
<td><apex:image url=”{!URLFOR($Resource.SIG001TOSIG010, ‘SIG002.png’)}” alt=”SIG002″/></td>
</tr>
</table>
</body>
</html>
</apex:page>
If you decide to use VisualForce to generate PDF documents, these can be used as input for SIGN Butler. You can use your VisualForce PDFs in SIGN Butler in the following way:
- Generate the PDF and select the PDF in Manual SIGN. Learn more about Manual SIGN here: Manual SIGN on the Academy
- Launch the SIGN Request automatically via Embedded SIGN: Embedded SIGN on the Academy
