I have tried to change the folder where the document are stored in the E-signature API.
But when i do that the API cannot find those documents.
There is a special way to do that ?
Thank you for you responses.
The way to move envelope is to use this API endpoint. You should be able to see the envelope in the new folder. To list folder envelopes you can use
GET /restapi/v2.1/accounts/{accountId}/folders/folder_id?include_items=true
What do you see if you get envelope folder information with
GET /restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}?include=folders
Related
I'm not very familiar with DocuSign or its API and after playing around in Postman I'm still not sure if I'm able to:
Create an Envelope based on a Template
Attach a pdf doc to said Envelope
Send for signing.
In case I got it all wrong, I'm trying to do the following:
Get the pdf doc from a third party and send it for signing via DocuSign. The document will be the same format every time(same signature placement, names, etc) except for data in it and it will be sent to the same people for signatures.
Is it possible to do so? Am I looking at right stuff?
Yes, this is completely possible. We in fact have existing Postman requests that do just that:
https://www.postman.com/docusign/workspace/docusign-s-public-workspace/request/14257714-ef2d10ba-b540-4644-93a1-b0344c0dd82c
Examples number 15 to 18 are the ones you want to look at.
To get started with our Postman collection, you can watch our youtube video: https://www.youtube.com/watch?v=mV73U2tg9c0&t=6s
I am trying to figure out how to use multiple URLs in a Connect-Rest in Pega 7.3 to connect to DocuSign using the DocuSign Pega integration that is built by Pega.
I have a specific link that contains API keys that I am required to use as the resource path in my Connect-Rest. However, I also have another link that calls a specific instance of DocuSign so that the info from Pega goes directly to the DocuSign instance.
I know that Pega has updated their connect-rest functionality in the current version but my question is does anyone know if there is a way to incorporate multiple urls into one connect-rest.
Thank you in advance.
I don't know what you mean by "connect-rest."
DocuSign has the "Connect" feature for sending webhook notifications when an envelope's status changes. All envelope sent by selected (or all) users will be monitored. You can create multiple Connect subscriptions so that multiple URLs will be sent when an envelope's status changes.
DocuSign also has "individual envelope webhooks." This feature is configured when an envelope is created via the API and the create request includes the EventNotification attribute. A maximum of one URL can be set per envelope.
If you are invoking Connect-Rest from a pega activity, you can capture the relevant URL as variable and pass that to function call to 'Connect-Rest' within activity. Another useful way maybe to use dynamic system setting and use #(Pega-RULES:Utilities).getSystemSetting() function to read the value of URL saved in the Dynamic system settings
I've used this tutorial to create a document service API and the documents are uploading just fine. I'm trying to delete a document now, but there doesn't seem to be much information on that subject.
Can I delete a document with a Delete request and the document ID or what is the best practice?
Yes, you should delete request by passing the document id.
If you are using java CMIS client library, then Session#delete methods should be used.
Best Regards,
Saurav
I have looked through the DocuSign documentation, StackOverflow and Google but without success.
When creating a package, is it possible to restrict signers to be able to view certain pages of the document ?
Let's say my borrower Lisa Smith should not be allowed to see the pages 5 to 10 while a second borrower can only be allowed to see pages 1 to 5, is that possible to do within the Rest API ?
Thanks
You can use the DocuSign document visibility feature.
If you send a document containing multiple files and you want to control which files each recipient sees, you can use document visibility to accomplish this. A common scenario is you want recipients to see only those files which they need to sign. With document visibility, you can create one document with files intended for individual recipients, rather than having to create a separate document for each recipient.
Using Document Visibility you can set access at document level. However setting access at page level is not supported.
See this answer on how to set documentVisibility using the rest api.
For more context, look for the excludedDocuments property on this page.
Is there a way to restrict the documents types that a signer can upload using the signer attachment? There does not seem to be a way to do this when setting the template. I would like to prevent users from uploading exe or other binary files.
There is currently no way for you to specify which file types to restrict, however the DocuSign platform has certain restrictions already in place.
When you use the Signer Attachment tab in your envelopes only file types that are considered "documents" are allowed as attachments, since once you attach them it shows as another page. Therefore, the recipient can not attach .exes or other binary files. You should be able to confirm this through some quick tests in the demo (developer) environment.