This is the first part of sending 2 Adobe Acrobat sign documents and a welcome letter to a client email address that was triggered from a SharePoint list. The data will be dynamically populated from the list to fields in the Acrobat sign document and the welcome letter.
It is not exactly what everybody might need, but has lots of tips to help you with your own Microsoft Automate flow projects and SharePoint.
1) The trigger. SharePoint - For a selected Item. Self explanatory :-) When you have rows in a SharePoint list. You would select the record and then click the automation tab your flow will appear.
2) SharePoint - Get Item. Gives you accesses to the list fields and potential data.
3) A date convertor component. Further on in the agreement, a DOB (date of birth - a date field) is needed. Dates come out in UTC format these components convert the formatting to your area or preference. A little more later on.
4) Another date convert. Name them to make easier for identification Top right - the 3 dots in a component.
5) Select an Adobe connector - "Create an agreement from a library template and send for signature."
At this point, you need to create a .pdf file. (the form that the recipient receives). The .pdf file needs to be in your Adobe cloud files as a Template. The libraryDocumentId - (to identify which .pdf/file to send) is a bit tricky to get/determine. I could not find it anywhere (really poorly done on Adobe's part.) How hard could it be?, select the file and see properties or something. Anyway, if you search online the only results were found was to run commands through the API. I did not have access to the API at the time. I got it by logging into the adobe account and opening the .pdf with it open look at its URL of the agreement in the browser's address bar. The ID usually starts with CBJCH.
On creating forms to use as a pdf. You can use excel to design your forms and print to .pdf. I find the Adobe web based designer to be just awful with limited design abilities and frustrating snap to settings that can not be disabled. You can use MS Word or any software that can print to a .pdf printer (built-in on windows 10)
More about the Adobe component/connector
Signature type: ESIGN
Means the primary interaction is to have the document signed by the recipient.
Participant Email - 1. Where/whom to send to. Can come from your SharePoint list - an email address field - as to where it would be sent. Select from the dynamic list.
Agreement Name - can be whatever you like.
In the web based UI of Adobe you will be configuring your .pdf form. For example, you drag the signature block over on the form to where it should be positioned.
You can further customize your forms with custom and dynamic values from your SharePoint list. In Adobe, you would drag over a text block and position on your form. You will name that text block and make it read only (it will show the value in the text block that you made in Adobe. See the above image Form Field Name - 1
Form field value: choose your field from the Power Automate dynamic list.
Redirect delay. After the recipient signs and clicks/taps submit, you can delay and then link to a website/resource.
Dates and decimals: Any time you need these data types. You need to convert the output to your proper format. Using expressions or convert components. Furthermore, they don't like NULL values. If any of the date/decimals fields can be (possibly) NULL configure the component(s) run after settings. The setting will allow a NULL value and the flow will just continue - instead the flow would fail.
In the image below a NULL value warning even after the successful run was complete.
