package created via fast track

Are you using just the UI and not the API/SDK? If you only have access to the UI, I believe this is your only option. This would be a good enhancement request though, as I can see how you might want a different package name. You can always create a post about this in the enhancement ideas forum. The project management team monitors that forum for ideas from customers. Also, posting in this forum also gives others a chance to +1 your idea if they like it, possibly giving more priority to your request. If you're using the API/SDK, you could simply create your own Fast Track functionality where you could name the Package anything you want in your custom code after someone submits the form you create in your application. Let me know. I'll check around to see if there's something else I'm not thinking of that could be done from the UI side as well.

Thanks Michael for your response. We want to see if the product has a way to address the situation we have. The problem with API/SDK route could be that we'll also have to take over the email notification aspects along with naming the package. This seems like a too custom a solution to implement. please advise

What email notifications would you need to take over if using the api/sdk? I'll talk to a product manager to see if anything is in the plan about being able to have some index value or another indicator to distinguish the transactions from each other when using fast track. Can you describe the scenario in which this is causing an issue so I can have more information when speaking to them? Thanks!

I am talking about the default emails that are sent out to the sender & signers as part of the signing ceremony where in the package is included as attachment upon. I was not sure if renaming the package using API/SDK will affect the email content at all.

When you create a package with the API/SDK, the automated emails from eSignLive still happen. You could also set up and expiration date and reminders to be sent out automatically. There should be no change in the email content. The same email templates are used no matter how the package is created, I believe. Those templates can be modified by contacting our support team. You definitely don't have to start doing the notifications yourself if you use the API/SDK. In any case, if you used the API/SDK, the only thing you should have to do is create your front end form and the code to create the package when the form is submitted. With the API/SDK, you could still even use a template, if you wanted, or simply access the files from your server/db or wherever they're stored. That would be up to you. Then, create a signing session and use the URL in an iframe or open in a new window for the user to be able to sign right away, like in fast track. Do you already have a license agreement with us? If so, do you have an integrated license to be able to use the API/SDK? I have also asked a product manager if there is anything in the plan to add an option to the fast track feature to differentiate the package names with an index or the packageId or something. I'll let you know what I hear back.

So, if we modify the package name programatically to say 'test'. After the signing ceremony has been completed, when the email notification is sent out to the signers & the sender, it includes the package as an attachment in the email. Will the package have the name 'test' or the default name that was system generated?

It would have the name of the package. So, in your example, it would be test.pdf and not templateName.pdf. However, if you just used the same base name or template name and added an index of some sort (00001, 00002, etc) or even their first initial and last name that they enter (templateName_mwilliams), you could still keep a similar naming convention while still eliminating/reducing duplicate names.

okay thanks. And just to reconfirm, the email that gets sent out after package completion will also have test.pdf & not templateName.pdf?

I may have misspoken on the name of the pdf file. The file will be the name of the document in the transaction. If you dynamically created your packages, you could name the documents specific to the user's name or an index and the download file would have the name you specified. As for the email, the email would contain the name of the transaction as you named it. "documents are available for 'template name' package" or whatever the words are. If you made a custom name for the package/transaction in your custom code, this would be the name reported in the email. Hope this clears everything up.

thank you Michael.