For years, many Salesforce (SFDC) developers have integrated DocuSign APIs into their SFDC applications. Today we’re releasing several new recipes for the Salesforce and force.com platforms to provide additional help and code examples to our SFDC developers. The recipes’ user experience layer includes Lightning and VisualForce pages.

These recipes can be used to extend the capabilities of DocuSign for Salesforce. DocuSign for Salesforce is a prerequisite for all of the following:

  • The SFDC Signing Requests recipe was built with Lightning. It’s a proof of concept (POC) for multiple use cases including having your SFDC community members (e.g. Partners, customer, employees) quickly sign agreements from within your community portal. This recipe shows how to set up a “Signing Request” custom object in SFDC and it includes the related Lightning components. Employees with DocuSign accounts create signing requests. Then your partners or anyone else within your partner or regular community portal can sign the documents using embedded signing. Your partners don’t need to leave your community to sign and they don’t need a DocuSign account!

sfdcblog_signingrequestsScreenshot showing Signing Request custom object.

  • The SFDC Auto-provisioning recipe is a POC for automating the common use case of adding a new partner to your SFDC portal after the partner has signed an agreement. This recipe shows how to set up a DocuSign Powerform to enable a new partner to initiate and sign a partner agreement with your company. Next, your employee counter-signs the agreement and decides which SFDC account record should be used for the new partner. Then the POC app automatically creates new contact and user objects in SFDC for the new partner and sends a welcome email message. You’ll be a hero! Why should your staff spend time creating SFDC objects after a new partner or customer signs when your app can do it automatically?

sfdcblog_autoprovisioningScreenshot showing contact (with an associated Partner User) that were both automatically provisioned by using the recipe.

  • SFDC Hello World shows how to send a DocuSign request from an Apex controller class. This recipe includes instructions for adding the DocuSign Signature SOAP WSDL file to your Salesforce org. Start with this recipe if you want to integrate SFDC and DocuSign.

sfdcblog_helloworldSFDC Hello World screenshot.

  • SFDC Embedded Sending demonstrates how an envelope can be sent from the Salesforce UX. Embedded signing enables the sender to directly upload documents to DocuSign. Apex “outcalls” to services such as DocuSign have limited maximum body sizes. Embedded sending can be used for large documents since they are uploaded directly to DocuSign, bypassing the SFDC file size limitations.

sfdcblog_embeddedsendingSFDC Embedded Sending screenshot.

  • SFDC Embedded Signing demonstrates how embedded signing can be used on Salesforce. With embedded signing, signers don’t need to click on an email link, they sign directly with Salesforce. Perfect for custom employee apps you’ve built on Force.com. Also great for signing from within your company’s Salesforce communities for partner, customers, suppliers, or employees.

sfdcblog_embeddedsigningEmbedded Signing screenshot.

Please let us know via apihelp@docusign.com what you’ve built with these recipes! Pull requests are welcomed if you have ideas for extending them. Don’t forget to signup for the DocuSign Developer Newsletter and visit the DocuSign Developer Blog.

(Visited 31 times, 1 visits today)