@Golding

Yes, It is possible to include those, if they are actually Envelope Custom Fields.

Examples: [[ECF:ECF field name]], [[Role_UserName]], [[Role_Email]]

You can find more details in this Docusign Support Article.

Hi Golding

The short answer is: No. What you need is Document Custom Field and NOT Envelope Custom Fields (I know it’s tricky)
I’ve recorded this quick video for you to give you more context

Hope this helps,
Sofian Saoudi | Founder @Solusign Consulting - Docusign Partner

Need help with Docusign?
 🌎  www.solusign.com | 📧 hello@solusign.com | 📺 Learn Docusign on YouTube 

@sofian_solusign @Golding 

Thank you for sharing and pointing out the important different between a document custom field and an envelope custom field. I want to add that you are able to set both type of custom fields via the CSV file in Bulk Send. So it is possible to achieve, but you may need to add a field, like position twice:

1. for a specific recipient as a document custom field (to be merged)
2. an envelope custom field (to be used in the email notification)

@Michael.Rave, that’s interesting, I’ve never seen this being mentioned in the documentation anywhere. Do you have a support article that shows that?

I might be a little slow here 😅 but can you provide an example?

Say we have a column in the CSV called ‘EIN’

What would be the syntax you’d use in the template email body/email message to reference that ‘EIN’ column in Excel?

@sofian_solusign

I am actually not sure this is documented in a single place in Docusign Support, but I can tell you from my experience that this is something that has been implemented for various customers already and working.

1. Create a envelope custom field (ECF) called “EIN” first in the account or on the template.
2. Then add a column with name “EIN” to the CSV file to pre-fill that ECF via bulk send.
3. Include the envelope custom field [[ECF:EIN]] into the email message or body to appear.
4. Send an envelope and use bulk send feature to upload the prepared CSV file to pre-fill.

The Docusign Support Article on Use Merge Fields in the Template Email Subject to Customize Envelopes contains the above mentioned ECF syntax.

The Sample-Bulk-Recipient CSV file that you can download for Bulk Send contains ECF examples columns and just need to be configured to the actual names, e.g. EIN here.

Putting these puzzle pieces together will result in the solution above, which fulfils that requirement.

@Michael.Rave thanks for letting me know.

So even though it’s not an actual ECF, following the ECF syntax works… ok!

I’ll test this!

@sofian_solusign 

It is an actual ECF that gets it’s filled from the CSV file used for bulk sending similar to not manually filling the document custom fields and using the CSV file to accomplish that.

The second part is just how to leverage an ECF in the email subject or body as document custom fields cannot be used here.

Good luck with testing and have a great day!

Hi Mrave

Really appreciate the solution you provided.  I tried this morning and confirmed it works perfectly fine.  

Hello ​@Michael.Rave or ​@sofian_solusign ,

I found this post via search and my question is simliar and I hope you are able to answer.

I created ECF (example: Customer_First_Name), in Salesforce I created a Merge Field with the following config:

• Object: Contact
• Field: First Name
• Name: Customer_First_Name
• Anchor Text: [[ECF:Customer_First_Name]]

and then placed [[ECF:Customer_First_Name]] in the Email Message. But no value show up. I also tried it with Quote Number.

Hope you can help me out.

Thanks and have a nice day,

Sven

​@ioSven

The merge field is a document custom field and not an envelope custom field, hence it does not work as you planned.

This Docusign Support article will give you additional insight on how to pre-fill existing ECFs from Salesforce which can then use in the email message.

Hi ​@Michael.Rave,

thanks for answering my post. To be clear, these ECFs can only be filed by hand and not with a value from a Salesforce Record? I like to use them in the Email Body as shown in the picture below.

Thanks and all the best,

Sven

​@ioSven 

Yes, that is what the article says.

The following rules apply to envelope custom fields in Salesforce:

• Only envelopes sent from standard Send with DocuSign buttons display envelope custom fields. Envelopes created from custom envelope template buttons do not display ECFs.
• Only envelope custom fields with Show field to envelope creators enabled display on the Recipients page.
• The Recipients page displays all envelope custom fields with Show field to envelope creators enabled.
• All "shown" ECFs from your DocuSign account display on the envelope Recipients page.
• Senders must enter values for all required fields to advance to the Prepare & Send page.
• Senders can add envelope templates to their envelopes on the Documents page. Adding templates imports template documents, recipients, and signature fields to the envelope.

I have not been working with Docusign in the context of Salesforce in a long time and I don’t have a personal environment anymore to try the current package at this point in time. I am pretty sure there is a way to set an email subject and message through configuration in Salesforce, so you may not need ECFs to achieve that.

Have you tried setting up an envelope configuration and setting the email subject as described here? That should enable you to pass values from Salesforce fields into the email subject and body without an ECF.

Another option to achieve this would be via the APEX toolkit, either via ECFs or email subject and body fields to dynamically include the values, but it’s probably more difficult to set up.

Hi ​@Michael.Rave ,

thanks for your reply. I was useing Learn How to Use Envelope Custom Fields in Salesforce because I’m not able to use the legacy setup.

But I’m not able to see the ECFs.

Thanks and all the best,

Sven