Skip to main content
Nintex Community Menu Bar
Knowledge Base

DocGen - Dynamic File Name when Using eSign Delivery Option

  • August 16, 2024
  • 0 replies
  • 69 views

Calderon_Doc
Nintex Employee
Forum|alt.badge.img+4

Topic

Sending a DocGen Package with Nintex eSign? Do you want the file to come back to Salesforce with an updated name? The following is a guide on how to achieve this dynamically.

 

Instructions 

 

Lets start in your Nintex AssureSign Portal
Click on View templates (simple setup) 

 

Click on Edit next to the template you want to use 

 

Click on the Document Manager button 

 

Click on the three dots – then click on Edit 

 

Enter [Document Name] in the Document Name field 
Click Save Document 

 

Back on the Edit Template screen Click on Edit sender input 

 

Click on Create Sender input 

 

In the Name field enter Document Name (If you always want to have data here make this required) 

Click on Save sender input 

 

Click Close 

Navigate to your DocGen package and create a delivery option 

Click on Electronic Signature 

 

Click on Nintex eSign 

 

Give your Delivery Option a name (ex: eSign) 

Select your Nintex eSign Account from the drop-down 

 

Click on the *Nintex eSign Template drop-down and select the template you want to use from your eSign account. 

Configure your Signer Details 

Click Save 

Take a look at your Nintex eSign as a Delivery Method 
You will now see a field under Sender Inputs labeled ‘Document Name’ 

 

You can update this field with <<tags>> from the DocGen Field Tagger  

Click Save 

When you generate this DocGen Package with the eSign delivery option it gets sent to the specified Signer(s). 

Once the Signer(s) have completed signing and the file is returned to Salesforce the file name will have been dynamically updated with the data pulled in by the <<tags>> specified. 

 

 

Additional Information

Please note that this is only one option to obtain this outcome. There could be another way to achieve this outcome. You will need to determine the best option for your use case. In our opinion, this is the most manageable option.

0 replies

Be the first to reply!