Getting an Agreement ID without opening the agreement

[Will Tyler]

I'm using API calls to read my agreement forms. The first thing I need to do is get the Agreement ID so I open up the PDF and pull it from the address bar. Then I can use the Agreement ID to get the Widget ID which I use to read the form fields. Now, I heard there's a way of getting the Agreement ID without opening the file. Does anyone know of such a thing or is that an urban legend?

[SimonESATS]

I assume the agreements themselves are not created via the API?

The above sounds like you open the agreement via the manage tab and then get the agreementID from the address bar.

My advanced uggestion is to make use of webhooks:

https://www.adobe.io/apis/documentcloud/sign/docs.html#!adobedocs/adobe-sign/master/webhooks.md

to notify you when an agreement is ready (or any other event leading up to that)

If that's out of scope, if you have Power Automate you can make use of Sign triggers to be notified. The notifications include the agreementID.

Another way would be to contact suport and ask them to enable the transactionID in the report export csv. When this is dne, run a report and export to CSV. IN the csv the transactionID=AgreementID.

[Will Tyler]

You are correct; the agreements are not created by API. There's a person who went through and created the templates.

So the way my situation works is that we're using UiPath. An email comes in saying we have a new agreement and then the automation goes into Sign and opens the file to get the ID and then uses an API call to get the widget ID to use an API call to extract the form information. I can already tell with the expected volume the chance of retreving the correct agreement from the manage tab is going to decrease rapidly.

It appears that webhooks, having to be hosted, would be a massive undertaking in and of itself and we're on a very tight deadline here. 

It appears my best option will be to try the report export CSV then the automation can read it from there. I'll check with my support team and if they can do this I'll come back and mark this as an accepted answer. Thank you! 

[SimonESATS]

fwiw I'm no a fan of RPA tools here seeing there are api methods to create agreements, (and thus returning you the agreementID as soon as the agreement is created. Though i appreciate it's easier said than done.

Re webhook same, but if your org is a MS 365 usre you may well have access to power automate and the Sign triggers are pretty much webhooks pre-packacged in a box.

As i the action to retrieve the form data.

So the Power automate flow can be triggered as soon as the agreemen is done, grab the form data and do something with it.

[Will Tyler]

The purpose of using UiPath is to take the information from the agreement
and put it into different order systems. Getting the information from the
form requires using the Widget ID, which is why I need the agreement ID,
because trying to read the form using the traditional RPA methods creates
either text that is broken (ie. W ill Ty ler) or reads the field names but
not the values. Even OCR was spotty.

--
Will Tyler
614-961-0656

[SimonESATS]

btw you may want t oedit your post to remove your number there!

Ah so Uipath is just used to grab the form data and not used to send agreements?

Form data can also be included into the report data export csv as well as the transaaction ID. I'm not sure if  form data is included by default these day, but if not support can help you to get that enabled for your account. 

That way Uipath can be used to trigger the report and it's download on a schedule, and grab the data from the csv.

btw if you have sharepoint Online, a completely different alterntive is to make use of the Sharepoint integration, and link the webform/widget with a sharepoint list:

https://helpx.adobe.com/sign/using/integration-guides.html

https://helpx.adobe.com/sign/using/microsoft-sharepoint-web-form-guide.html

[Will Tyler]

I can't edit my previous posts so guess my number is out there. 😞

The way this process is set up is a department creates the form and sends it to the client. The client fills the form out and signs it. The agreement is CC'd to an automation inbox. The automation monitors the box and when it sees there's a new email it kicks off the process to read the agreement then take the data and put it in the different systems.

This is where I'm having problems. If I go into Sign and manage I can open the form but I can't do anything to read it. The bot doesn't have the rights to export the data because it didn't create the form. 

No option for Sharepoint either. It's like any roadblock that can be dropped in front of me to get this to work is being dropped.

[SimonESATS · Accepted solution]

I can't recommend power automate enough for this :), but another option may be possible depending on how the cc is setup. Sign allows for a default or autmatic cc via account and group settings. 

Also in account/group global settings is the 

Collect form data with agreements

settings, which when enabled includes the form data as csv in the signed and filed email to the sender and the auto-cc. 

Note than any cc set on the send screens will not get this csv I don't think.

[Will Tyler]

You are correct that the CC'd recipients don't get a copy of the form data but a quick rule placement to forward the emails from the sender works just as well. Three months I've been working on trying to figure out how to work this. Thank you so much!