eSignatures via Power Automate with DocuSign and Adobe Acrobat Sign
Вставка
- Опубліковано 14 жов 2024
- In this video, look at how to use the DocuSign and Adobe Acrobat Sign connectors within Power Automate. In both cases, we start with a Word document in a SharePoint library, initiate the flow from a SharePoint list, use Power Automate to create the envelope/agreement, and then use separate flow(s) to handle the signature statuses and write the signed document back to the original SharePoint list item.
Hey Jeff! Thanks for the video. However, when I try to run this, it seems like Adobe is adding default fields to the end of the document like Email:____ Title:____ Company:____
How do I restrict it to just interpreting my custom {{*Signature}} line as the only field users should fill in?
We've seen some situations where Adobe Sign adds some of its own elements to the form. We had some success changing from Signature to Approval in that case, but that is just a guess. I no longer have my Adobe trial account and thus am unable to try this.
Excellent video. Thank you for the explanation.
Excellent Video.
Thanks Jeff. Question- what if we have multiple signers. My flow ends when one of the signers sign ? How does the flow check from one participant to the other?
I haven't done anything with multiple signers, but I believe you would handle that in the "listener" flow as you can detect when the workflow is finalized and when each signature occurs. Hope this helps.
Great Video, how do we manage multiple signers? Thank you very much.
Thanks for the kind words. I haven't done this but it looks quite possible in both DocuSign and Adobe. This link for DocuSign might be helpful: support.docusign.com/s/document-item?language=en_US&rsc_301=&bundleId=ulp1643236876813&topicId=kcb1578456479440.html&_LANG=enus. For Adobe, I think you would do this right within Adobe Acrobat Pro and select as a Signature 2 field. This link about the Adobe Portal might be usefu: helpx.adobe.com/sign/using/send-document-for-signature.html#:~:text=Adobe%20Acrobat%20Sign%20makes%20it,to%20multiple%20people%20to%20sign.
Hi Jeff, Thanks for the video!
I put the text tag like you in my word file, but when the flow run completed, I didn't get the signature request, only get a fill request and see nothing in the file, could you please share how you save your text tag in word file? Thank you.
Here is how my samples look in the Word documents.
DocuSign:
Name: /n1/
Address: /a1/
Signed: /s1/
Date Signed: /ds1/
Adobe:
Name: {{Name 1_es_:signer1:fullname:font(size=Auto)}}
Address: {{ Address}}
Signed: {{ *Signature 1_es_:signer1:signature}}
Date Signed: {{Date 1_es_:signer1:date:format(mm/dd/yyyy):font(size=Auto)}}
Hope this helps.
Hi Jeff - do you have a video that does this in reverse i.e. takes the responses from the envelope and populates columns in Sharepoint list? cheers, Mike
I actually cover that part within this video. Go to around the 14 minute mark for DocuSign and the 41 minute mark for Adobe Sign. Both are similar in that you create a flow for listening for the signing and other events. You then grab the ID and use that to look up the correct SharePoint list row. Then update it with the signed form, status, etc. Hope this helps.
Awesome video. Thanks.
Appreciate the nice feedback!
I am attempting to use a developer account because I need to send a second document after the first one is completed.
Is it possible to do this with a regular account?
When using the developer account, the subject line says Test Document and includes the message 'This document is for demonstration purposes only.' How can I address these two issues?
It sounds like you would need a licensed account to get rid of the that message.
so good man! Hope i can be as good as you !
Adobe Sign now requires an Enterprise license to use with power automate. They quoted me £550/year which I simply cannot justify for the creation of ~ 50 documents per year. Especially in addition to the Power Automate Premium license. Something to be aware of.
I had not heard that. Thanks for letting everyone know.
I just bought your book, and I'm fighting Adobe Sign and Power Automate trying to send out Agreements automatically. Argh! This is frustrating! Could I hire you for like an hour to do do a zoom call consultation? :) Not even kidding!
I can't do that unfortunately. But I have found that using Adobe Acrobat Pro if you have it makes the process much easier. You can use it to mark up your PDF file and even put in logic. Then use that as a template instead of the Word document like I used in my video. I couldn't find a good reference for that, but that is likely due to my search not being specific enough. This link for the Power Platform side looks pretty helpful: helpx.adobe.com/sign/integrations/microsoft-powerapps-flow.html#sign-to-power-automate.
@@jeffrhodes Fun fact: If you make your email address in the flow the same as your Adobe email address, it DOES NOT SEND. When I used one of my other email addresses, it worked fine. Sheesh. That would have been a handy piece of information. I"m still workingon figuring out how to put the data from the sharepoint list into my Adobe Sign agreement so it's all nice and pre-filled. :)
Edit: GOT IT!!!! See, what you have to do is pull up the Advanced Parameters drop down in the Create Agreement and Send for Signature action, and pick the "Form Field" option. Then you can just keep "Add Item"'ing for each field that you need, making sure (I think) to match the name of the field in the flow to the tags on the Word document beint used as a template, and populate the default values of same with the values from the Sharepoint List. Hoky smokes. This was tricky but is super useful once you figure it out. DId you ever make a followup video tothis that shows how to use Templates that live in Adobe Sign?
I need to see about adding the extra logic for tracking the Agreement status etc now within the Sharepoint List. :) :) :)
@@goodluckfox Good stuff! Thanks for sharing your lessons learned. I haven't made any follow-up videos unfortunately as I don't have Adobe Pro or Acrobat Sign on my personal machine. One nice DocuSign feature is the demo connector that doesn't require a license.
Hey Jeff, I've noticed the Adobe Sign Flow(2nd Flow) is not running now. It worked on Monday. Suddenly it stopped working today. I've created a new list again. Wrote the flows again. Re did everything. It still does not work. I do not get an error. The trigger is not even detected. When I go to run history, it does not popup. Is your flow working now? Can you help me out?
My Adobe demo account expired. Perhaps yours did as well? If not, you might go to Connections within Power Automate to see if any issues are showing there with Adobe Sign.
Jeff can you weigh in on why my Adobe Sign "esign" request ends up requiring that the recipient download the document, open it in Reader, and then sign it and send it back? I want to offer that Digital Signature without the need for these extra steps.
All I can think of is some sort of client-side setting. Have you tested by sending to yourself like I did in the video. Downloading and signing it pretty much defeats the purpose of course:).
Hi Jeff, is it ok to take a look at the sharepoint list for this video? mine does not work especilaly the docsign status
I don't share the SharePoint list unfortunately, but here is a link to a screen capture that shows the SharePoint list settings: plattecanyon-my.sharepoint.com/:i:/g/personal/jeffrey_plattecanyon_onmicrosoft_com/EUIOox2bPnxLmPno1Ru7lC4B4GbA7ItaUVHs2VabkesAQQ?e=9H03e2. Hope this helps.
Could you also create a compliant DMS with it?
can we add more fields to document like name, address, date etc. while using Adobe connector?
You can do it via the tags like I did in the video, but better looks to be to use Adobe Acrobat DC to configure the form template itself (and use a PDF rather than a Word document).
@@jeffrhodes thank you for your help
Trying to add a pdf file to the envelope before sending. My flow runs, but it sends the envelope without the file attached. I viewed the output and get these errors as I am trying to pull in the attachment from my Microsoft Forms upload, "errorCode": "UNSPECIFIED_ERROR", "message": "PDF validation failed". I even used the base64 expression. Hope you can help.
Did you change the type from docx to PDF? I have used PDF successfully but find that it makes the rest of the PDF "unfillable" (other than the tags that you put in via Power Automate).
@@jeffrhodes Yes, I changed the type to PDF and used the base64 expression to embed the dynamic content from my MS Form where the document was uploaded. The flow runs successfully, but the document is not added and when I check the output I see the above errors.
@@melindagildart7342 only other suggestion would be to try without the base64() part as that seems to vary based on each cloud. I would check that the error is on the creating the document action as getting the tags into the PDF file can be challenging (and cause errors). Hope this helps a bit.
@@jeffrhodes This is what I get when I don't include the base64() expression. "The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters."
@@melindagildart7342 And you changed your "Get file content via path" action to ensure it is pointing to the PDF file? Sorry - not many more ideas.
Hello, I have a problem when I send the envelope that it tells me "The email address for the recipient is invalid. The recipient Id follows."
Hard to say I would debug the flow and look closely at the address to make sure there are no stray characters. Either of these should send to any email address.
Is anyone else having trouble with the 'Get Items' action right before the 'Switch' one? It is telling me that "Column 'Certificate' does not exist. It may have been deleted by another user." How to fix?
This needs to be the original name of the column in SharePoint. I had named it Certificate and then renamed it to AgreementID. But the OData query wants the original name. The easiest way to find the correct name to use is to edit the column in SharePoint and then look at the URL: plattecanyon.sharepoint.com/samples/_layouts/15/FldEdit.aspx?List=%7BCAFDE37E%2D8780%2D4F96%2DB99E%2DF683F228C904%7D&Field=Certificate. The "Field=Certificate" part at the end is what you are looking for. If you are following my example and named it AgreementID initially, then use that instead. Hope this helps.
Why didn't open case 5 on the flow?
There are two Case 5's in the Adobe Acrobat Status flow. The first is "AGREEMENT_ACTION_COMPLETED". It then has a case for SIGNER, APPROVER, ACCEPTOR, FORM_FILLER, and CERTIFIED_RECIPIENT. For all of these, I just update the Message variable to log the agreement name and participant. For example, here is the value for CERTIFIED_RECIPIENT (case 5): Notification from Microsoft Power Automate The receipt of the Adobe Sign agreement @{triggerBody()?['agreement']?['name']} has been acknowledged by @{triggerBody()?['participantUserEmail']}. Hope this helps.
Thank you @@jeffrhodes 👍
Excellent Video.
Thanks for the nice words!