Moving from code managed signature placement to Templates

Hi Josh,

Thanks for your post! "Is optional" toggle button should appear like below:

If it's not visible in your designer page, kindly create a support ticket ([email protected]) and our support agent would help you check your account settings and reply back to you in short time. (Or if you are in Sandbox environment, you can share your account's email to [email protected] so that I can have a quick look into this for you)

Duo

Email sent

There is no "Is Optional" option for me in the sandbox.esignlive.com environment

Thank you, I see it now.

A followup question:

Up until now (with all packages / signatures managed in CODE), we've been able to create a package, and attach multiple documents to it (illustrations, applications, etc..) as needed.

Now that we have a template, the only way to use it in code is one for one (1 package = 1 template). Is there no way to attach multiple templates to a package for signing?

Scenario:

We have Illustrations and Needs Analysis that are dynamically generated (IE code managed doc builders)

We have static applications for Life, Annuity, and Final expense that we are moving to templates because they are static.

Our thought was to create a template per static document (Life template, Annuity template, Final expense template), then, when creating our package, we would attach everything needed (whether dynamic or templated) for one package.

But this doesn't seem to be supported. As far as I can tell, we would have to send out a package per template, and then one combined package for the dynamically generated things. Is this correct? Or is there a better way?