@lg125689
I suggest to add an envelope custom field (ECF) to the template, where you enter the unique number. Make it mandatory so the sender needs to provide a value. You can include the ECF placeholder in the email subject in your template.
The other option is to leave the document name in the email subject and manually rename the document before sending, This is not as intuitive as the solution with the ECF, but both options work to achieve this.
Not sure if you want to change the document name or send emails with subject including the po#. if you want to change the name you can do that with a step in clm called rename document. If you want to put that in the subject line of an email, you can have a variable for po# and add it to the subject line.
Purchase Order Type #6_ABC Inc_<%#Variable.PO#%>
Hi @Michael.Rave. I explored the Envelope Custom Field option and this would do exactly what we need except that I left out the fact that we are using a DocuSign-Smartsheet integration whereby the DocuSign template is automatically populating and routing based on the information in our Smartsheet when triggered. We are able to pull names and email addresses into our template routing and can fully populate the underlying PDF template but I do not see a way to connect Smartsheet data to the Envelope Custom Field. We might be able to theoretically add in the information using the “correct” envelope feature but that would be a fairly disorganized and inefficient workaround. Any ideas on how to solve this? As mentioned, if we were routing documents right out of DocuSign ECFs would be an ideal solution.
We would have the same issues with the second option since we are triggering automation in Smartsheet to route DocuSign envelopes and so are not regularly accessing DocuSign directly.
@lg125689
That is indeed an important fact. I am not deeply familiar with the connector from Smartsheet to Docusign, so I cannot tell you, if that connector allows to provide values for envelope custom fields or not.
Most connectors that are being developed by partners like Smartsheet, initially have a specific scope and only implement those features their design team has identified. Unfortunately, envelope custom fields is often not available and needs to be added by the partner. Having build several connector myself I can tell that it is not complicated, but someone needs to spend a few hours to implement and test it.
The connector is being developed by Smartsheet, so raising an enhancement request with them to add this feature to the connector may lead to this being available in the future.
Hello @lg125689 ,
If you found the provided response to be a useful solution to your question, please mark it as the best answer by clicking “Select as Best” to make it easier for other users to find.
Best regards,
Nathaly | Docusign Community Moderator
"Select as Best" below if you find the answer a valid solution to your issue!