Skip to main content
L
luconsta
Inspiring
April 21, 2020
Answered

Create Word Document with signer tags and use Power Automate to sign in specific placeholders

  • April 21, 2020
  • 1 reply
  • 5613 views

Hello,

I am new to AdobeSign and I have a project where I have to cover two main challenges.

 

First one is to create a Microsoft Word document that would be signed by multiple departments. For the sake of the example I would say there are just two departments. I have found some literature about Adobe Sign Text Tag Guide but is not clear how could I create these tags in Word but I found that is it somehow possible because it mentioned that:

Adobe Sign text tags can be placed in any document type such as PDF, Microsoft Word, PowerPoint, Excel and text files (.txt, .rtf).

 

The second challenge is to use that tags in Power Automate (former known as Microsoft Flow). I have also found a good starting point in Adobe Sign for Microsoft PowerApps and Flow but this "tags part" is either not documented or did not found it yet.

 

So there are two questions I would like some help:

1. Is this kind of scenario/challenges achievable?

2. There is a step-by-step documentation/demo that could be followed for using signer tags?

 

Kind Regards,

Lucian

Correct answer luconsta

Hello,

 

It seems that after a lot of trials and errors I have found the answer, and solved both challenges, so I will try explain my findings for me (just in case I will forgot some of them), or for the others that will need it.

 

Used to read "one row or another" it seems that this time I have skiped an important part for the tag guide mentioned above for use in Word: "The entire span of the text tag, from the beginning curly brace to the closing curly brace, must fit within a single line."

And one other problem - the tags between curly braces {{ and }} are not fields as I have thought in the first place (inserted in Word with CTRL+F9) are just plain and simple text. 

So I have used tags like this:

{{Dep1Name_es_:signer1:fullname     }} - for full name of the first signer

{{Dep1Sign_es_:signer1:signature    }} - for the signature of the first signer

 

Then the second challenge was simpler because following the samples in the second documentation provided above, in the step "Create an agreement from an uploaded document and send for signature" where I have completed in order the Recipient Email/Signing Order/Role.

Initially I was "lost" in the "Form Field Name/Value" pairs but none of them was required (at least in my case).

 

Kind Regards,

Lucian

1 reply

L
luconstaAuthorCorrect answer
Inspiring
April 21, 2020

Hello,

 

It seems that after a lot of trials and errors I have found the answer, and solved both challenges, so I will try explain my findings for me (just in case I will forgot some of them), or for the others that will need it.

 

Used to read "one row or another" it seems that this time I have skiped an important part for the tag guide mentioned above for use in Word: "The entire span of the text tag, from the beginning curly brace to the closing curly brace, must fit within a single line."

And one other problem - the tags between curly braces {{ and }} are not fields as I have thought in the first place (inserted in Word with CTRL+F9) are just plain and simple text. 

So I have used tags like this:

{{Dep1Name_es_:signer1:fullname     }} - for full name of the first signer

{{Dep1Sign_es_:signer1:signature    }} - for the signature of the first signer

 

Then the second challenge was simpler because following the samples in the second documentation provided above, in the step "Create an agreement from an uploaded document and send for signature" where I have completed in order the Recipient Email/Signing Order/Role.

Initially I was "lost" in the "Form Field Name/Value" pairs but none of them was required (at least in my case).

 

Kind Regards,

Lucian

    J
    Joe30647463a7r2
    Participant
    August 26, 2023

    Hi Lucian, I know this a quite old thread now, but I'm having some issues with the signature fields, specifically - and wondered if you saw the same behaviour at all. 

    I am using the "create an agreement from a file and send for signing" action, in power automate. In the Merge Data field, I've got the body of a list item (which contains all the personal info such as name/emails etc which need to be passed through to the fields in the contract). 

    Those tags work perfectly fine, and are rendered correctly in the agreement which gets created in Adobe Sign. (In other words, the data being passed to Adobe Sign from Power Automate is appearing correctly in the PDF document.

     

    However, the signature and check mark fields are NOT rendering properly. They just show up as the plain text, {{Sig_es_......}} and Adobe Sign is creating new fields for the signatures (and email addresses) automatically and adding these below my plain text tags. 

    Did you encounter this during your troubleshooting? I can't figure out how to get Adobe Sign to place the signature boxes where I'm adding the tags, instead of ignoring the tags, still rendering them as text, and then placing new signature boxes below them on the next page. 

    L
    luconstaAuthor
    Inspiring
    August 28, 2023

    Hi @Joe30647463a7r2 ,

    Unfortunately I did not see this behavior, and I don't know other information except the one already posted here.

    You might try create a new post with your issue, but the answers in this forum tends to arrive in months or years... 😞

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices