Send envelope - replacing multiple template documents












0















I have a question regarding the following scenario.



I have a Docusign template with 2 documents. Template contains two Template Roles with few signature tags applied on documents. There could be also Text Input tags, checkbox tags etc...



What I need is to send an envelope with documents that will replace both template documents but to apply DocuSign tags (signature, checkbox..) that were configured in the template, to apply document visibility, and as much DS template features as it can.



Signature request (envelope) is sent using DocuSign.eSign C# client library.
I'm using following code that builds Composite Template that contains two new documents with appropriate documentIDs retrieved from DocuSign template.



 EnvelopeDefinition envDef = new EnvelopeDefinition();
envDef.EmailSubject = "Subject";
envDef.EmailBlurb = "Body";

envDef.CompositeTemplates = new List<CompositeTemplate>();
envDef.CompositeTemplates.Add(new CompositeTemplate
{
ServerTemplates = new List<ServerTemplate> {
new ServerTemplate
{
Sequence = "2",
TemplateId = "TEMPLATE_ID_GOES_HERE"
}
},
InlineTemplates = new List<InlineTemplate>
{
new InlineTemplate
{
Sequence = "1",
Documents = new List<DocuSign.eSign.Model.Document>
{
new Document
{
DocumentBase64 = "...", //document content
Name ="some.pdf",
DocumentId = "TEMPLATE_DOC1_ID_GOES_HERE" //ID of template document that should be replaced
},
new Document
{
DocumentBase64 = "...", //document content
Name ="another.pdf",
DocumentId = "TEMPLATE_DOC2_ID_GOES_HERE" //ID of template document that should to be replaced
}
}
}
}
});


Envelope is successfully sent, signers can see both new documents, but there are no Tags that were configured in the Template (on Docusign Web UI), and I'd like to avoid sending recipient tabs from client.



Am I missing something?



Thanks.










share|improve this question

























  • Composite templates can definitely get tricky and complex the more in-depth you go, on the surface though I can't see anything obviously wrong with your code. One thing I was never clear on was the full scope of the sequence param, just as a test have you tried swapping the order of the server and inline templates and making both sequence = 1? I might try a few tests around that to help diagnose...

    – Ergin
    Nov 16 '18 at 21:04
















0















I have a question regarding the following scenario.



I have a Docusign template with 2 documents. Template contains two Template Roles with few signature tags applied on documents. There could be also Text Input tags, checkbox tags etc...



What I need is to send an envelope with documents that will replace both template documents but to apply DocuSign tags (signature, checkbox..) that were configured in the template, to apply document visibility, and as much DS template features as it can.



Signature request (envelope) is sent using DocuSign.eSign C# client library.
I'm using following code that builds Composite Template that contains two new documents with appropriate documentIDs retrieved from DocuSign template.



 EnvelopeDefinition envDef = new EnvelopeDefinition();
envDef.EmailSubject = "Subject";
envDef.EmailBlurb = "Body";

envDef.CompositeTemplates = new List<CompositeTemplate>();
envDef.CompositeTemplates.Add(new CompositeTemplate
{
ServerTemplates = new List<ServerTemplate> {
new ServerTemplate
{
Sequence = "2",
TemplateId = "TEMPLATE_ID_GOES_HERE"
}
},
InlineTemplates = new List<InlineTemplate>
{
new InlineTemplate
{
Sequence = "1",
Documents = new List<DocuSign.eSign.Model.Document>
{
new Document
{
DocumentBase64 = "...", //document content
Name ="some.pdf",
DocumentId = "TEMPLATE_DOC1_ID_GOES_HERE" //ID of template document that should be replaced
},
new Document
{
DocumentBase64 = "...", //document content
Name ="another.pdf",
DocumentId = "TEMPLATE_DOC2_ID_GOES_HERE" //ID of template document that should to be replaced
}
}
}
}
});


Envelope is successfully sent, signers can see both new documents, but there are no Tags that were configured in the Template (on Docusign Web UI), and I'd like to avoid sending recipient tabs from client.



Am I missing something?



Thanks.










share|improve this question

























  • Composite templates can definitely get tricky and complex the more in-depth you go, on the surface though I can't see anything obviously wrong with your code. One thing I was never clear on was the full scope of the sequence param, just as a test have you tried swapping the order of the server and inline templates and making both sequence = 1? I might try a few tests around that to help diagnose...

    – Ergin
    Nov 16 '18 at 21:04














0












0








0


1






I have a question regarding the following scenario.



I have a Docusign template with 2 documents. Template contains two Template Roles with few signature tags applied on documents. There could be also Text Input tags, checkbox tags etc...



What I need is to send an envelope with documents that will replace both template documents but to apply DocuSign tags (signature, checkbox..) that were configured in the template, to apply document visibility, and as much DS template features as it can.



Signature request (envelope) is sent using DocuSign.eSign C# client library.
I'm using following code that builds Composite Template that contains two new documents with appropriate documentIDs retrieved from DocuSign template.



 EnvelopeDefinition envDef = new EnvelopeDefinition();
envDef.EmailSubject = "Subject";
envDef.EmailBlurb = "Body";

envDef.CompositeTemplates = new List<CompositeTemplate>();
envDef.CompositeTemplates.Add(new CompositeTemplate
{
ServerTemplates = new List<ServerTemplate> {
new ServerTemplate
{
Sequence = "2",
TemplateId = "TEMPLATE_ID_GOES_HERE"
}
},
InlineTemplates = new List<InlineTemplate>
{
new InlineTemplate
{
Sequence = "1",
Documents = new List<DocuSign.eSign.Model.Document>
{
new Document
{
DocumentBase64 = "...", //document content
Name ="some.pdf",
DocumentId = "TEMPLATE_DOC1_ID_GOES_HERE" //ID of template document that should be replaced
},
new Document
{
DocumentBase64 = "...", //document content
Name ="another.pdf",
DocumentId = "TEMPLATE_DOC2_ID_GOES_HERE" //ID of template document that should to be replaced
}
}
}
}
});


Envelope is successfully sent, signers can see both new documents, but there are no Tags that were configured in the Template (on Docusign Web UI), and I'd like to avoid sending recipient tabs from client.



Am I missing something?



Thanks.










share|improve this question
















I have a question regarding the following scenario.



I have a Docusign template with 2 documents. Template contains two Template Roles with few signature tags applied on documents. There could be also Text Input tags, checkbox tags etc...



What I need is to send an envelope with documents that will replace both template documents but to apply DocuSign tags (signature, checkbox..) that were configured in the template, to apply document visibility, and as much DS template features as it can.



Signature request (envelope) is sent using DocuSign.eSign C# client library.
I'm using following code that builds Composite Template that contains two new documents with appropriate documentIDs retrieved from DocuSign template.



 EnvelopeDefinition envDef = new EnvelopeDefinition();
envDef.EmailSubject = "Subject";
envDef.EmailBlurb = "Body";

envDef.CompositeTemplates = new List<CompositeTemplate>();
envDef.CompositeTemplates.Add(new CompositeTemplate
{
ServerTemplates = new List<ServerTemplate> {
new ServerTemplate
{
Sequence = "2",
TemplateId = "TEMPLATE_ID_GOES_HERE"
}
},
InlineTemplates = new List<InlineTemplate>
{
new InlineTemplate
{
Sequence = "1",
Documents = new List<DocuSign.eSign.Model.Document>
{
new Document
{
DocumentBase64 = "...", //document content
Name ="some.pdf",
DocumentId = "TEMPLATE_DOC1_ID_GOES_HERE" //ID of template document that should be replaced
},
new Document
{
DocumentBase64 = "...", //document content
Name ="another.pdf",
DocumentId = "TEMPLATE_DOC2_ID_GOES_HERE" //ID of template document that should to be replaced
}
}
}
}
});


Envelope is successfully sent, signers can see both new documents, but there are no Tags that were configured in the Template (on Docusign Web UI), and I'd like to avoid sending recipient tabs from client.



Am I missing something?



Thanks.







docusignapi docusigncompositetmplts






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 25 '18 at 20:45









Larry K

34.2k1174102




34.2k1174102










asked Nov 16 '18 at 13:35









Slavisa PokimicaSlavisa Pokimica

1




1













  • Composite templates can definitely get tricky and complex the more in-depth you go, on the surface though I can't see anything obviously wrong with your code. One thing I was never clear on was the full scope of the sequence param, just as a test have you tried swapping the order of the server and inline templates and making both sequence = 1? I might try a few tests around that to help diagnose...

    – Ergin
    Nov 16 '18 at 21:04



















  • Composite templates can definitely get tricky and complex the more in-depth you go, on the surface though I can't see anything obviously wrong with your code. One thing I was never clear on was the full scope of the sequence param, just as a test have you tried swapping the order of the server and inline templates and making both sequence = 1? I might try a few tests around that to help diagnose...

    – Ergin
    Nov 16 '18 at 21:04

















Composite templates can definitely get tricky and complex the more in-depth you go, on the surface though I can't see anything obviously wrong with your code. One thing I was never clear on was the full scope of the sequence param, just as a test have you tried swapping the order of the server and inline templates and making both sequence = 1? I might try a few tests around that to help diagnose...

– Ergin
Nov 16 '18 at 21:04





Composite templates can definitely get tricky and complex the more in-depth you go, on the surface though I can't see anything obviously wrong with your code. One thing I was never clear on was the full scope of the sequence param, just as a test have you tried swapping the order of the server and inline templates and making both sequence = 1? I might try a few tests around that to help diagnose...

– Ergin
Nov 16 '18 at 21:04












1 Answer
1






active

oldest

votes


















0














Change the sequencing order so the new documents are listed first.



With composite templates, order matters. For documents, the earlier documents are used. -- So your new documents should be before the server template (and its documents).



For everything else, the later information wins.



See this answer: https://stackoverflow.com/a/44376770/64904



On second thought, I see that you're doing this and it is all working except that the tabs are not being applied to the new documents.



Try the merge_roles_on_draft query parameter. Also, if you're using anchor tabs, add the applyAnchorTabs: 'true' element to the document objects.






share|improve this answer

























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53338942%2fsend-envelope-replacing-multiple-template-documents%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Change the sequencing order so the new documents are listed first.



    With composite templates, order matters. For documents, the earlier documents are used. -- So your new documents should be before the server template (and its documents).



    For everything else, the later information wins.



    See this answer: https://stackoverflow.com/a/44376770/64904



    On second thought, I see that you're doing this and it is all working except that the tabs are not being applied to the new documents.



    Try the merge_roles_on_draft query parameter. Also, if you're using anchor tabs, add the applyAnchorTabs: 'true' element to the document objects.






    share|improve this answer






























      0














      Change the sequencing order so the new documents are listed first.



      With composite templates, order matters. For documents, the earlier documents are used. -- So your new documents should be before the server template (and its documents).



      For everything else, the later information wins.



      See this answer: https://stackoverflow.com/a/44376770/64904



      On second thought, I see that you're doing this and it is all working except that the tabs are not being applied to the new documents.



      Try the merge_roles_on_draft query parameter. Also, if you're using anchor tabs, add the applyAnchorTabs: 'true' element to the document objects.






      share|improve this answer




























        0












        0








        0







        Change the sequencing order so the new documents are listed first.



        With composite templates, order matters. For documents, the earlier documents are used. -- So your new documents should be before the server template (and its documents).



        For everything else, the later information wins.



        See this answer: https://stackoverflow.com/a/44376770/64904



        On second thought, I see that you're doing this and it is all working except that the tabs are not being applied to the new documents.



        Try the merge_roles_on_draft query parameter. Also, if you're using anchor tabs, add the applyAnchorTabs: 'true' element to the document objects.






        share|improve this answer















        Change the sequencing order so the new documents are listed first.



        With composite templates, order matters. For documents, the earlier documents are used. -- So your new documents should be before the server template (and its documents).



        For everything else, the later information wins.



        See this answer: https://stackoverflow.com/a/44376770/64904



        On second thought, I see that you're doing this and it is all working except that the tabs are not being applied to the new documents.



        Try the merge_roles_on_draft query parameter. Also, if you're using anchor tabs, add the applyAnchorTabs: 'true' element to the document objects.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 25 '18 at 20:59

























        answered Nov 25 '18 at 20:50









        Larry KLarry K

        34.2k1174102




        34.2k1174102
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53338942%2fsend-envelope-replacing-multiple-template-documents%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Create new schema in PostgreSQL using DBeaver

            Deepest pit of an array with Javascript: test on Codility

            Costa Masnaga