SIGN BUTLER V2 – Embedded Sign

Build your own SIGN Butler experience from internal SFDC, Communities, Guest User Application forms, Sites, portals, … Sign Butler V2 API

See it in action:

Embedded SIGN demo

Example of code for Lightning Web Component:

Code example

Notes for Guest User or unauthenticated usage: #

For this type of usage, it is better to use the same set as explained here: Field Service Lightning (FSL) – Embedded SIGN via FSL App

The example is about usage in the FSL App but the URL generated for Embedded Sign can be used from every application, so it can also be opened via Guest User Site. This URL will:

1. Create the PDF to be signed
2. Create the SIGN Request
3. Forward to the signing page for the first signer

The creation of the URL can also be done via the APEX API (cadmus_sign2.SignButlerClientApi.getEmbeddedSignUrl) but then the User (Guest, Community/Experience, SFDC) have to have:

1. SIGN Butler license
2. Have permissions on all SIGN Butler SObjects: Community / Experience Cloud – Partner / Customer
3. Have permissions on all SIGN Butler APEX classes. Use or copy from the “SIGN Butler User” permissionset
4. Have SFDC sharing rules for Guest User to all SIGN Butler SObjects to be able to use the data (eg SIGN Request Template) required

If you do not want want to use the Embedded SIGN Url and use the code example above that generates the PDF first and then use this PDF to launch the Embedded SIGN. Then make sure that:

1. PDF and SIGN Butler license is assigned
2. All PDF and SIGN Butler SObjects permissions are set
3. Have permissions on all PDF and SIGN Butler APEX classes. Use or copy from the”PDF Butler User” and “SIGN Butler User” permissionsets
4. Have SFDC sharing rules for Guest User to all PDF and SIGN Butler SObjects to be able to use the data (eg SIGN Request Template) required.
5. Have SFDC sharing rules for Guest User to all Salesforce data required to generate the PDF