I send the document to DocuSign in draft status. Then user(contract owner) logs into DocuSign, adds additional signers and tags then sends the document for signing.
Is it possible to get the original unsigned document(pdf) that was sent after the document is completed via the API?
The reason I need the original document is to make sure that the user(contract owner) has not changed/modified the document in DocuSign.
I want to make sure the signed document is exactly the one I sent via API.
DocuSign does not have granular permissions to block changes to the documents when the Envelope is in draft status.
Re: Is there a way to get back the original unsigned document that was sent to DocuSign after it is signed/completed?
Answer: unfortunately, no. As soon as original documents are uploaded to DocuSign, they are converted into a "flat" (no logic) PDF. The original document is then discarded.
As a workaround, you could programmatically create a template, then create an envelope from the template. Then the user could tag the document without the ability to change the document. See use case 8, creating a template programmatically for code examples. These are on the eg-03 series of examples. Eg, the PHP code example.
Or better, update your application to tag the documents for the user.
We are investigating the idea of enabling the documents in an envelope to be locked. Please ask your DocuSign business or support contact to add your company information to DocuSign internal issue number SMPI-236.
Related
I've been reading the whole documentation related to Acrobat API for document sign.
According to documentation after registering an account, one must create an application inside the Admin UI. For that application one receives the Client ID and Secret. Every request has known parameters like redirect uri, response type, scope, state, etc.
I have been not fortunate with the examples in the documentation and what is most important, some colleagues state it is not necessary to create an application and work with client id and secret, that the only thing initially necessary is to get the Authorization token.
I need to be in the right direction, what are the end points for a testing accounts, where to find the shard. The documentation varies and the end points are just examples, not real ones.
The functionalities I must implement are related to get access token, generate embedded document, get document content, etc.
Thanks in advance
I have several PDF file stored in Salesforce, I need to send each PDF to each different external users (external users that don't have Salesforce access) in a secure way.
I see two ways:
Encrypt the PDF and send it encrypted to the user mail address, then send the password by SMS.
Allow the external users to access the PDF stored in Salesforce using a user-password but without having a Salesforce user.
Is there any solution for one of the two ways?
Thanks,
Jaime
Content Documents (the actual table name for what you see as Files / Chatter Files / Notes) might have an option for #2. The old school Documents and Attachments - unlikely.
You can password protect the links and / or make them expire after certain date. Read up https://help.salesforce.com/s/articleView?id=sf.content_delivery_create.htm&type=5
Here's ERD: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_erd_content.htm
Alternative could be the "sign" apps on AppExchange. Check Adobe Sign, Docusign (or whatever is the name). But I suspect they're just think integrations and docs are hosted in different cloud, your organisation might have security issues with that.
We are developing for one of your customers a method from our application (written exclusively in LiveCode Script) and need to utilise SOAP via a POST command directly from LiveCode. I eventually, after a lot of digging into the resources pages, found some reference on how to Post 'CreateAndSendEnvelope' from here:
CreateAndSendSchema
However, it does not show where to place login credentials for the user or company or whatever so that it is attributed to the correct account.
I found this question here which kind of points me in the right direction, but do you not have any specific documentation on how to set up your headers and body when using XML for both authenticating and sending a document via email using SOAP?
Providing a simple guide demonstrating the header required and the basic XML to POST to send a document with tags for signing to a single recipient by email using a senders user credentials would be perfect.
Thanks
Sean.
Pi Digital Productions Ltd
SOAP is still using what we call "Legacy Auth" which is the older, less secure, (not OAUTH) authentication.
To use that, you still need an IK (Integration Key) but you provide the username, password and IK in clear text inside a header called X-DocuSign-Authentication that looks like this:
'X-DocuSign-Authentication: { "Username":"DocuSign#example.com", "Password":"DocuSign_password", "IntegratorKey":"DocuSign_Integrator_Key" }'
Let's say we receive a PDF document that is alredy signed.
We'd like to add a new signature field to the document and send it to the person that needs to sign it inside our environment.
We've seen that it's possible with AcrobatPro to directly sign the document, but it's not possible to just add the signature field to the document without signing it. We don't have AcrobatPro licenses for every user on the organization that have to sign external documents, so we're looking for a way to prepare the document for them, so they can sign it just within Acrobat Reader.
We are on a quite big organization (around 3000 ppl) and our ERP already manages everything related to signatures to our own documentation, but we are seeking for a solution to sign external documents that already have been externally signed while our provider evolves a solution inside the ERP.
Use case: My system needs to retrieve authorization forms from a variety of sources. There is no standard form - each source may define their own authorization form, but each authorization form requires exactly one signature. None of the blank forms will have PDF signature field markup - they will just be simple PDFs originally meant for printing and wet signing. For example, every summer camp in the country has their own release form. My system will receive those forms and present them for signature, without knowing what the form looks like ahead of time.
This means I will not have the chance to mark up the form with DocuSign "Sign Here" boxes.
Is it possible in DocuSign to have a system send in a form and allow the signer to manually determine exactly where they want to place their signature? Without giving the signer duties such as preparing the document themselves - I just want them to see the form on screen, and be prompted to "Click wherever you think you should sign", just like they would do in the paper world.
You can use DocuSign free form signing for your usecase.
See this DocuSign Blog Post for more information.
Free-form signing occurs when no tags are placed on a document submitted via DocuSign. This means that the signer will be presented with a palette of signature options (Signature, Initial, Full Name, etc.) which can be applied to the document at will.