eSignature Implementation Webinar Slides


Published on

Slides from the DocuSign eSignature Implementation webinar 3/23/11

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

eSignature Implementation Webinar Slides

  1. 1.
  2. 2. Hour 1: DocuSign User Interface and Administration<br />Presenter: Mike Parish<br />
  3. 3. DocuSign ConsoleRemote SigningSendingTemplates<br />
  4. 4. Signer Receives Email invitation from the Sender<br />Signer Clicks<br />‘Review Documents’<br />
  5. 5. Signer Instructions<br />Signer provided instructions prior to reviewing the documents<br />Signature Adoption at 1st Signing tab<br />
  6. 6. Review Document – Signer Guided<br />
  7. 7. Signatures and Data Complete – Confirm Signing<br />
  8. 8. DocuSign Concepts<br />Envelope<br />Template<br />
  9. 9. What is a DocuSign Envelope?Documents = What do we need Signed<br />
  10. 10. What is a DocuSign Envelope?Recipients = Who acts on the envelope<br />
  11. 11. What is a DocuSign Envelope?Email Subject and Messaging<br />
  12. 12. What is a DocuSign Envelope?DocuSign Tabs = Signer Tasks<br />
  13. 13. What is a DocuSign Envelope?Reminders and Expirations<br />
  14. 14. What is a DocuSign Template?Templates = Envelope Draft<br />
  15. 15. Using DocuSign<br />Sending Envelopes<br />Managing Envelopes<br />
  16. 16. Hour 2: Utilizing DocuSign for Salesforce<br />Presenter: Mike Borozdin<br />
  17. 17. Agenda<br />Review DocuSign System<br />What is an envelope<br />What are DocuSign accounts and members<br />Review different ways to use DocuSign from<br />Understand the API function groups<br />Understand the DocuSign system architecture<br />Set up a simple 1-click send scenario<br />Getting started: DocuSign DevCenter<br />
  18. 18. DocuSign Envelopes<br />End User Definition:<br />A DocuSign Envelope is a secure digital file containing one or more documents being sent for signature. Documents can be placed into a DocuSign envelope by either ‘printing’ them into the envelope using the DocuSign print helper, or by uploading them. A DocuSign envelope can contain any document you can print, and no special formats are needed.<br />A DocuSign Envelope is a tremendous improvement on a familiar paper metaphor – the overnight express envelope, but it does much more than a traditional envelope can. A DocuSign Envelope is capable of ensuring the proper sequence of signing, makes sure each signer signs, fills out, and initials all the required locations specific to them, and prevents unauthorized users from being able to sign or even see the documents it contains.<br />Computer Science Definition<br />A transaction container which includes documents, recipient information and workflow<br />
  19. 19. General Architecture<br />Accounts<br /><ul><li>Branding
  20. 20. Expiration
  21. 21. Publishing
  22. 22. Password Requirements
  23. 23. Document Retention
  24. 24. And other features!</li></ul>Members<br /><ul><li>Sending envelopes, signing, administer</li></ul>Recipients<br /><ul><li>Don’t need an account – actors in the signing transactions</li></li></ul><li>Different ways to DocuSign from<br />
  25. 25. DocuSign API Function Groups<br />Sending<br />Signing<br />Post Processing<br />Status and Managing<br />Administrative<br />
  26. 26. API Functions<br />Sending:<br />CreateAndSendEnvelope and CreateEnvelope | CreateEnvelopeFromTemplates |<br />SendEnvelope | RequestSenderToken<br />Signing:<br />RequestRecipientToken<br />Post Processing Functions:<br />RequestDocumentPDFs | RequestDocumentPDFsEx | DocumentPDF | RequestPDF | EnvelopePDF |TransferEnvelope | ExportAuthoritativeCopy<br />Status and Managing:<br />CorrectAndResendEnvelope | EnvelopeAuditEvents | GetStatusInDocuSignConnectFormat | RequestCorrectToken | RequestStatus and RequestStatusEx | RequestStatuses and RequestStatusesEx | Ping | PurgeDocuments | SynchEnvelope | VoidEnvelope<br />Administrative:<br />GetRecipientEsignList | GetRecipientList | RemoveAddressBookItems | RequestTemplate | RequestTemplates | SaveTemplate | UpdateAddressBookItems | UploadTemplate | Embedded Callback Event Codes<br />
  27. 27. Walkthrough Step 1: get accounts and set up access<br />Before getting started you need to get a free developer account at and a free DocuSign developer account at<br />Start out by adding DocuSign webservices to your authorized endpoints for your developer account. To do this, go to Setup > Security > Remote Sites and add <br />
  28. 28. Walkthrough Step 2: Set up a site<br />For the purpose of this walkthrough you just need to have a site for testing. You can get to the screen below by clicking Setup > Develop > Sites. <br />
  29. 29. Walkthrough Step 3: Create Render Contract Page<br />Page Code:<br /><apex:pagerenderAs="pdf" standardController="Contract"><br /> <apex:detailrelatedList="true" title="true"/><br /> <div style='clear:right;margin-top:50px'><br /> <div style='float:right'>____________________________________</div><br /> <div style='float:right'>By:</div><br /> </div> <br /> <div style='clear:right;margin-top:50px'><br /> <div style='float:right'>____________________________________</div><br /> <div style='float:right'>Date Signed:</div><br /> </div> <br /></apex:page><br />The page needs to be added to the site to ensure that you can access it for testing. You can accomplish that by going to the site detail and selecting Site VisualForce Pages.<br />The other setting that has to be adjusted for testing is adding Contracts as something that is accessible from this site. To accomplish this go to Public Access Settings and edit the standard object permission.<br />
  30. 30. Walkthrough Step 4: Create The Proxy Class<br />Sending WSDL:<br /><br />Go to the Apex Classes and select “Generate from WSDL”. When the class generator asks you to supply a class name, we suggest that you overwrite the class name with DocuSignAPI. <br />
  31. 31. Walkthrough Step 5: Create Custom Controller<br />public with sharing class SendToDocuSignController {<br /> private final Contract contract;<br /> public String envelopeId {get;set;}<br /> private String accountId = '';<br /> private String userId = '';<br /> private String password = '';<br /> private String integratorsKey = '';<br /> private String webServiceUrl<br /> = '';<br /> public SendToDocuSignController(ApexPages.StandardController controller)<br /> {<br />this.contract = [select Id, CustomerSignedId, AccountId, ContractNumber<br /> from Contract where id = :controller.getRecord().Id];<br />envelopeId = 'Not sent yet';<br />SendNow();<br /> }<br /> <br /> public void SendNow()<br /> {<br />DocuSignAPI.APIServiceSoapdsApiSend<br /> = new DocuSignAPI.APIServiceSoap();<br />dsApiSend.endpoint_x = webServiceUrl;<br /> <br /> //Set Authentication<br /> String auth = '<DocuSignCredentials><Username>'+ userId<br /> +'</Username><Password>' + password <br /> + '</Password><IntegratorKey>' + integratorsKey<br /> + '</IntegratorKey></DocuSignCredentials>';<br />System.debug('Setting authentication to: ' + auth);<br />dsApiSend.inputHttpHeaders_x = new Map<String, String>();<br />dsApiSend.inputHttpHeaders_x.put('X-DocuSign-Authentication', <br /> auth);<br />DocuSignAPI.Envelope envelope = new DocuSignAPI.Envelope();<br />envelope.Subject = 'Please Sign this Contract: ' <br /> + contract.ContractNumber;<br />envelope.EmailBlurb = 'This is my new eSignature service,'+ <br /> ' it allows me to get your signoff without having to fax, ' +<br /> 'scan, retype, refile and wait forever';<br />envelope.AccountId = accountId; <br /> <br /> // Render the contract<br />System.debug('Rendering the contract');<br />PageReferencepageRef = new PageReference('/apex/RenderContract');<br />pageRef.getParameters().put('id',contract.Id);<br /> Blob pdfBlob = pageRef.getContent(); <br /> // Document<br />DocuSignAPI.Document document = new DocuSignAPI.Document();<br />document.ID = 1;<br />document.pdfBytes = EncodingUtil.base64Encode(pdfBlob);<br />document.Name = 'Contract';<br />document.FileExtension = 'pdf';<br />envelope.Documents = new DocuSignAPI.ArrayOfDocument();<br />envelope.Documents.Document = new DocuSignAPI.Document[1];<br /> envelope.Documents.Document[0] = document;<br /> // Recipient<br />System.debug('getting the contact');<br /> Contact contact = [SELECT email, FirstName, LastName<br /> from Contact where id = :contract.CustomerSignedId];<br />DocuSignAPI.Recipient recipient = new DocuSignAPI.Recipient();<br />recipient.ID = 1;<br />recipient.Type_x = 'Signer';<br />recipient.RoutingOrder = 1;<br />recipient.Email = contact.Email;<br />recipient.UserName = contact.FirstName + ' ' + contact.LastName;<br /> // This setting seems required or you see the error:<br /> // "The string '' is not a valid Boolean value. <br /> // at System.Xml.XmlConvert.ToBoolean(Strings)" <br />recipient.RequireIDLookup = false; <br />envelope.Recipients = new DocuSignAPI.ArrayOfRecipient();<br />envelope.Recipients.Recipient = new DocuSignAPI.Recipient[1];<br /> envelope.Recipients.Recipient[0] = recipient;<br /> // Tab<br />DocuSignAPI.Tab tab1 = new DocuSignAPI.Tab();<br /> tab1.Type_x = 'SignHere';<br /> tab1.RecipientID = 1;<br /> tab1.DocumentID = 1;<br /> tab1.AnchorTabItem = new DocuSignAPI.AnchorTab();<br /> tab1.AnchorTabItem.AnchorTabString = 'By:';<br /> <br />DocuSignAPI.Tab tab2 = new DocuSignAPI.Tab();<br /> tab2.Type_x = 'DateSigned';<br /> tab2.RecipientID = 1;<br /> tab2.DocumentID = 1;<br /> tab2.AnchorTabItem = new DocuSignAPI.AnchorTab();<br /> tab2.AnchorTabItem.AnchorTabString = 'Date Signed:';<br />envelope.Tabs = new DocuSignAPI.ArrayOfTab();<br />envelope.Tabs.Tab = new DocuSignAPI.Tab[2];<br /> envelope.Tabs.Tab[0] = tab1; <br /> envelope.Tabs.Tab[1] = tab2; <br />System.debug('Calling the API');<br /> try {<br />DocuSignAPI.EnvelopeStatuses<br /> = dsApiSend.CreateAndSendEnvelope(envelope);<br />envelopeId = es.EnvelopeID;<br /> } catch ( CalloutExceptione) {<br />System.debug('Exception - ' + e );<br />envelopeId = 'Exception - ' + e;<br /> }<br /> }<br />}<br />
  32. 32. Walkthrough Step 6: Get your DocuSign API creds<br />
  33. 33. Walkthrough Step 7: Creating the 2nd Page<br /><apex:pagestandardcontroller="Contract" extensions="SendToDocuSignController"><br /><h1>Your eSignature request is being sent to DocuSign API!</h1><br /><hr/><br /><apex:form ><br /><apex:commandButton value="Send Again!" action="{!SendNow}"/><br /></apex:form><br /><hr/><br /><strong>The DocuSign EnvelopeId:</strong>{!envelopeId}<br/><br /></apex:page><br />Now you can test the controller class:<br /><br />
  34. 34. Walkthrough Step 8: Adding a button<br />Go to Setup > Customize > Contracts > Buttons and Links and create a New button.<br />In the properties, select Detail Page Button and then add the URL with the Contract Id: /apex/SendToDocuSign?id={!Contract.Id}<br />Add the button to the page layout for the Contract object. <br />
  35. 35. Getting Started: DevCenter and Professional Services<br />Free Sandbox Account<br />SDK<br />Sample Code<br />Forums<br />Webinars<br />Professional Services<br />Over 350 Integrations<br />Design, Architecture and Implementation<br />
  36. 36. Hour 3: Using the DocuSign API<br />Presenter: Julia Ferraioli<br />
  37. 37. DocuSign API Resources<br />SDK with example projects in<br />C#<br />Java<br />PHP<br />Ruby<br />Apex<br />hosted at<br />Active developer community<br />hosted<br />broken down by language and topic<br />Online/Offline API documentation<br /><br /><br />
  38. 38. Live Coding Demo<br />Using .NET framework<br />Follow along in the cookbook posted on the forums:<br /><br />
  39. 39. Hour 4: Successfully Completing DocuSign Certification<br />Presenter: Julia Ferraioli<br />
  40. 40. Outline<br />Why do I need to certify?<br />DocuSign Marketplace<br />When certification is necessary<br />Fees and other information<br />How to be prepared for the meeting<br />Preparing a demo<br />Sample demo, or the meta-demo<br />What happens after certification<br />Next steps…<br />
  41. 41. Why do I need to certify?<br />Important change from the demo environment to production environment<br />Need to ensure that the behaviors that occur in development are sustainable and scalable<br />Confirm that the application complies with certain guidelines and standards<br />Most of all, we want to make you as successful as possible!<br />
  42. 42. DocuSign Marketplace<br />Listing of applications that add value to the DocuSign service<br />Being included in the DocuSign Marketplace gives you access to reviews, download statistics and greater visibility<br />Getting certified gives you the option of being included in the DocuSign Marketplace!<br />
  43. 43. When certification is necessary<br />Your integration with DocuSign is near complete,<br />Your product is ready to go live and<br />You are certain that there will be no major behavioral changes to your integration with DocuSign<br />When certification is not necessary<br /><ul><li>You have made small changes to your integration, or
  44. 44. You have made changes to parts of your product that do not affect the integration</li></li></ul><li>Fees and other information<br />SMB<br />$995 per certification<br />Enterprise<br />$2500 per certification<br />Typically take from 45 minutes to an hour (less if prepared!)<br />Aim to minimize the number of certifications your application needs<br />
  45. 45. How to be prepared for the meeting<br />Fill out your certification checklist<br />Prepare a demo of your integration<br />Make sure you can explain the security protocols of your integration<br />Test your error handling for when you cannot reach DocuSign<br />Know how to capture the trace of an envelope<br />Audit your own API calls<br />
  46. 46. Preparing a demo<br />When preparing your demo, you will want to test several use cases. Some cases are: <br />User declines to sign<br />User’s information is incorrect<br />Sender voids the envelope<br />User takes more than one session to sign<br />Application cannot connect to DocuSign<br />Someone resets your DocuSign credentials<br />
  47. 47. API Rate Limits in Place!<br />To maintain reliability and stability within our demo and production environments, DocuSign has operated with certain API call efficiency guidelines. To ensure effective load balance, we continually monitor the API calls in our backend systems and reach out to work with developers putting unnecessary burden on the system. Going forward, DocuSign will implement an API Call Rate Limit to further balance loads on the system.<br />Effective March 1, the demo environment ( will be limited to a call rate of 1,000 API calls per hour per account<br />Effective April 1, the production environment ( will be limited to a call rate of 1,000 API calls per hour per account<br />Please note that when the API call rate limit is reached you will receive an exception on every call for up to 60 minutes, until the next hour starts.<br />
  48. 48. Sample Demo, or the meta-demo<br />
  49. 49. Avoid Problems and Use These Best Practices<br />Problems:<br /><ul><li>Polling our system
  50. 50. Using the wrong authentication
  51. 51. Not handling errors</li></ul>Best Practices:<br /><ul><li>Use the E-mail subject for better search.
  52. 52. Put recipient specific messages into the recipient note
  53. 53. Use Connect Events instead of polling</li></li></ul><li>What happens after certification<br />We sign off on your checklist<br />You set up a meeting to finalize your account configuration<br />You submit your integrator’s key to be moved to production<br />
  54. 54. Next steps…<br />Change your endpoints to point to production<br />Cease any polling behaviors you may have in our demo environment<br />Remember, our demo environment is only for active development<br />Continue to use our demo environment for any code changes<br />Production is for code that has been thoroughly developed, tested and certified<br />Remember, re-certification is only necessary for new functionality, code paths or framework changes<br />
  55. 55. Q & A<br />
  56. 56. Thank you!<br />