DocuSign

DocuSign is one of the leading digital signature platforms globally and we’re excited to announce that you can now send your WebMerge documents directly to DocuSign to collect signatures!  Like our other e-signature integrations, you can send documents out to multiple signers, CC other parties, plus collect any additional information from the signers. All of this is seamless with WebMerge and DocuSign combined.

To demonstrate how this integration works, we’re going to show you how to create dynamic contracts (we’ll show/hide certain sections based on conditions for each contract) from Salesforce, then we’ll send that contract over to DocuSign for signature.

To get started, let’s setup our contract template in WebMerge.  This template is where we’ll define the merge fields that we’ll be populating with data from Salesforce.  For this example, we’re going to setup our template using Word and then we’ll upload the file to WebMerge when we are finished.

In our document (template) we define our merge fields with text tags (just type them into the Word document) like {$CustomerName} or {$Billing_Address}.  Here’s what our contract looks like:
 


Now, let’s take a look at how we can make this contract more dynamic and only show certain sections depending on the state where the customer is located.  For this we’re going to use some simple “if” statements that will determine the state.  For example:

{if $CustomerState == ‘CA’}
    Under California Law, we are required to disclose this information.  At any time either party is able to terminate this contract without cause.  There is a minimum 30 day notification.
{/if}{if $CustomerState == ‘AZ’}

    Under Arizona Law, we are required to release this information.  At any time either party is able to terminate this contract without reason, but must submit written notice at least 60 days prior to the desired termination of the contract.
{/if}


Here’s what this looks like inside the rest of our contract:
 


We’re also going to define where we want the signatures to go inside our contract.  We can do this with special text tags defined by DocuSign.  In our signature block, we’re going to use anchor tags like: \s1\ and \s2\.  For more information, see bottom of article.
 


Once you’ve finished up the contract, log into WebMerge and create a New Document and choose Office Document as the document type.  This will allow you to upload your Word document to WebMerge from your computer.  Go ahead and upload your file.

Great, now we’re ready to get this contract hooked up to DocuSign so that we can get it signed by our customers!  Under the Deliver tab inside WebMerge (after you’ve edited any settings in the setup process), go ahead and add a New Delivery then choose DocuSign.  You should see something like this:
 


First, you’ll need to login to your DocuSign account.  This will give WebMerge access to upload documents to your account.  Go ahead and enter your login information and click the button.  Once you enter the correct login information, the page will refresh and you should see the options to setup signers.

Go ahead and select the name and email address for the signers you want included on this contract.  If you do not have any merge fields in your document for the signer name or email address, select <<other>> from the dropdown, then type in the merge field like {$signer_name} or {$signer_email}.  This will add those as merge fields to your merge process (it will not place them inside your document).
 


Once you have DocuSign setup, our last step is going to be hooking up Salesforce to send information to WebMerge to generate the contract.  We’re going to use the WebMerge managed package to integrate our Salesforce org with WebMerge.  Inside the package, you are going to setup a new Mapping for this contract.  We are going to hook up the mapping to our Opportunity object and select our new Contract from the document dropdown.
 


Go ahead and click the continue button and on the next step, you’re going to see a list of the merge fields that are in your contract.  For each merge field, you need to select which Salesforce field that “matches” up to.  Here’s what our finished mapping looks like:
 


After you’ve saved the field mapping, go ahead and Save and Active the mapping.  This will activate the mapping and make it available for users in your Salesforce org to use.
Now it’s time for a quick test!  Jump over to one of your opportunities (we suggest using a test opportunity) and click the WebMerge button on that record, then select the new Contract mapping that you just setup.  This is going to send the opportunity information over to WebMerge and we’ll generate the contract then hand it off to DocuSign.  You should receive an email from DocuSign with a link to sign the document.
 


That’s it!  Once you’ve (or your customer has) signed the document, you will receive a final signed copy of the contract.  How’s that for easy?!  Can you think of other ways that you could use WebMerge and DocuSign to streamline your document generation and signature process?
 

Docusign for Salesforce

If you are integrating with Salesforce and you want the signed document saved in Salesforce, you can send the Record ID of the record using a custom field (under More Options) called: DSFSSourceObjectId

You also have to turn on settings inside DocuSign.  Click here for more info.

 

DocuSign Anchor Tags

 Embedding signatures and fields in your document can be done by adding anchor tags to your template that look like: \s1\

Here's a list of available anchor tags:

Description Short Tag Long Tag
(Turn on under More Options)
Signature \s1\ \signature1\
Initial \i1\ \initial1\
Date \d1\ \date1\
Name \n1\ \name1\
Title \t1\ \title1\
Attachment \attachment1\
\attachment1_2\
\attachment1_3\

\attachment1_req\
\attachment1_2_req\
\attachment1_3_req\
\attachment1\
\attachment1_2\
\attachment1_3\

\attachment1_req\
\attachment1_2_req\
\attachment1_3_req\
Text Box \tbx_1_text\
\tbx_1_2_text\
\tbx_1_3_text\
\tbx_1_text\
\tbx_1_2_text\
\tbx_1_3_text\
Checkbox \cb_1_yes\
\cb_1_2_yes\
\cb_1_3_yes\
\cb_1_yes\
\cb_1_2_yes\
\cb_1_3_yes\
Radio Button \rb_1_1a\
\rb_1_1b\
\rb_1_1c\
\rb_1_1d\
\rb_1_1e\
\rb_1_1a\
\rb_1_1b\
\rb_1_1c\
\rb_1_1d\
\rb_1_1e\
Radio Button
(required)
\rb_1_1_req\
\rb_1_2_req\
\rb_1_3_req\
\rb_1_1_req\
\rb_1_2_req\
\rb_1_3_req\
Have more questions? Submit a request

24 Comments

  • Avatar
    Michael Barnathan

    How do you place more than one checkbox for an individual signer to check? Checking one \cb_1_yes\ tag checks all of them, and custom tags don't seem to work.

     

    Update: cb_1_2_yes, cb_1_3_yes, etc. (but not cb_1_1_yes?) seems to work.

    Edited by Michael Barnathan
  • Avatar
    Jeremy Clarke

    Hi Michael,

    Yes, that's correct, you can use cb_1_2_yes, cb_1_3_yes, etc, but the first one is only cb_1_yes

    Thanks!

  • Avatar
    Colin Cook

    Jeremy, do I need to escape my Docusign anchor tags somehow in my Word template? I am entering /s1/ directly into Word and that is what is showing up inside the PDF that is rendered by Docusign.

  • Avatar
    Michael Barnathan

    Backslashes, \s1\ :)

  • Avatar
    Michael Barnathan

    You'll also have to make them white or otherwise conceal them, Docusign will place its fields on top of them but won't erase them from the document.

  • Avatar
    Colin Cook

    Put \s1\ into my Word doc and made it white but Docusign is not swapping out my token for a signature element in their UI. Advice?

  • Avatar
    Jeremy Clarke

    Hi Colin,

    Try changing the output of your document to PDF. It looks like DocuSign is having a hard time reading the Word document.

  • Avatar
    Colin Cook

    I got it.

    I was using /s1/ but in the More Options part of the Data Route Delivery tab I had the "Use full name anchor tags (signature1, initial1, date1, etc)" option selected.

    It's working now

  • Avatar
    Stephen Pocock

    How can I insert the signing tags into a pdf using Nitro PDF?

    I have tried using form text boxes pre-filled with \initial1\ and \i1\, I have tried using text too.

    The only way I seem to be able to get Docusign to see a signature is required is if there is a signature form field. But I cannot allocate those to a signer. It just forces the first person to sign the box.

    I should add that this is from a PDF that is inserted into the merge from a dataroute. Would this be the issue? Does webmerge further encode the tags during the merge process?

    Thanks

    Stephen

  • Avatar
    Jeremy Clarke

    Hi Stephen,

    You need to add the signing tags as text in the PDF, not inside text boxes. Please reach out to support and send us your file so we can take a look.

    Thanks!

  • Avatar
    Albert Trevino

    I have done some testing and the anchor text does not disappear when signing the document. It is converted from a word to PDF. For example the signed date and signature will show over text anchor tag I put in the word document. What am I doing wrong?

  • Avatar
    Jeremy Clarke

    Hi Albert,

    Please change the font color of your anchor tags to white or a light gray and that will fix the issue :)

    Thanks!

  • Avatar
    Pablo Mantecon

    Hello,
    We are testing DocuSign + Salesfoce + Webmerge and we'd like to get information back in Salesforce when the document has been signed.

    The only info that I've found about this is the DSFSSourceObjectId custom field, which I couldn't set up with the information in this article. Could you help?

    I guess this option would send the signed document back to Salesforce. Would it be possible to, for example, update the Quote stage to "signed" when the contract has been signed?

    Thanks a lot in advance

  • Avatar
    Jeremy Clarke

    Hi Pablo,

    After you setup the custom field in your DocuSign delivery for DSFSSourceObjectID, you need to turn on that feature inside DocuSign. Check out this documentation: https://support.docusign.com/en/articles/DocuSign-for-Salesforce-Adding-Completed-Documents-to-the-Notes-and-Attachments1

    Thanks!

  • Avatar
    Uma Shankar

    Hello,

    Will I be able to preview the document before sending the contract out through Docusign?

    Thanks!

  • Avatar
    Jeremy Clarke

    Hi Uma,

    Unfortunately, there isn't a way to preview the documents before they are sent out to DocuSign - everything happens automatically.

    That being said, if you happen to be using Salesforce, the latest version of our managed package has a "preview" functionality that will generate a watermarked document.

    Thanks!

  • Avatar
    Uma Shankar

    Hi Jeremy,

    Yes - we are using Salesforce and i was able to update the webmerge package but I am not really sure how to enable "preview" functionality within salesforce. Can you please point me to a documentation for preview configuration?

    Thanks!

  • Avatar
    Jeremy Clarke

    Hi Uma,

    If you look under your Mapping settings (WebMerge Mappings > Edit) there's a checkbox option to allow the document to be previewed.

  • Avatar
    Pablo Mantecon

    Hi Jeremy,

    I've got a follow up question on the one I asked you a couple of days ago.
    Thanks for clarifying the setup on the DocuSign side, very helpful.

    I'm still facing the issue with the webmerge side.
    When I'm setting up the Docusing delivery I can click on "More options" and then "Use custom fields".
    There I have "Name" = "Value".
    I guess Name is DSFSSourceObjectId, but what's the value?
    I don't have merge fields to select there, and I can't make it work with "QuoteId" and things like this. What should I put in there? do you have any example?

    Thanks a lot in advance!

  • Avatar
    Jeremy Clarke

    Hi Pablo,

    You can enter any merge field in that box, so go ahead and enter {$QuoteId} then inside your Salesforce Mapping, you'll see "QuoteId" as a merge field and you'll need to match that up to the record ID field from the dropdown.

  • Avatar
    Pablo Mantecon

    Hi Jeremy,

    Thanks a lot.
    I still couldn't make it work. Maybe I'm trying to do something that is actually impossible?
    My customer is planning to use Webmerge and Docusign, but not the Docusign for Salesforce App.
    My assumption was that if we're able to send the document through Webmerge+Docusign delivery, then we can sync info back to Salesforce by using this article. So there's no need to pay for the "DocuSign for Salesforce" App.
    Am I right?
    I'm happy to jump into a call if you need more information.

    Thanks and best regards.

    Pablo

  • Avatar
    Jeremy Clarke

    Hi Pablo,

    Ahh, you would need to use DocuSign's SF app as well. I have a different solution for you. We allow you to "delay" deliveries until the DocuSign signing process is complete, so if you setup a Salesforce delivery on your document, then go under "More Options" on your DocuSign delivery, you'll see an option to "Delay deliveries until signing is complete" -- Check that box and then pick the SF delivery.

    That should do the trick!

  • Avatar
    Pablo Mantecon

    Hi Jeremy,

    Again, thanks a lot. It helped!
    Now we're using some anchor tags as \tbx_1_text\.
    They appear as mandatory when the customer receives the document via DocuSign. These are optional fields and don't necessarily need to be filled. How can I make them optional?

    Thanks and best regards.

    Pablo

  • Avatar
    Jeremy Clarke

    Hi Pablo,

    They shouldn't be required - we are not setting the "required" parameter in the API call, so DocuSign should be defaulting to optional.

Please sign in to leave a comment.
Powered by Zendesk