I have requirement to use docusign to send documents for sign.
I have gone through the documentation of api of it but could not found way for below requirement:
Signature Verification
Online viewer/editing
Does docusign provide these functionality?
Thanks.
1) When you create an electronic signature you get a unique id that is encrypted, documentable and tamper-evident.
You can set your electronic signature verification preferences such as time stamp, digital certificate and more. Signer authentication options include identity verification via email address, SMS text message, phone call, unique access codes, and more.
2) You can only make changes to a DocuSign document when the sender enables you to use the Mark Up feature. If the feature is enabled, you can:
"White out" or cover up document text to indicate deletions.
Cover up text and add new text over the old text.
Add new text in a blank region of the document.
You cannot alter the document once it is signed for obvious reasons.
The following file formats are supported
DocuSign supports the following file types:
DOCUMENT .as, .asl, .asp, .doc, .docm, .docx, .dot, .dotm, .dotx, .htm, .html, .pdf, .pdx, .rtf, .txt, .wpd, .wps, .wpt
DRAWING .dwg, .dxf, .emz, .svg, .svgz, .vdx, .vsd, .vss, .vst
IMAGE .bmp, .cdr, .dcx, .gif, .ico, .jpg, .jpeg, .pct, .pic, .png, .rgb, .sam, .tga, .tif, .tiff, .wpg
PRESENTATION .dps, .dpt, .pot, .potx, .pps, .ppt, .pptm, .pptx
SPREADSHEET .csv, .et, .ett, .xls, .xlsx, .xlt
Related
I am interesting in obtaining the file type (e.g. PDF, Word doc) of documents sent in an envelope. Of course this could be done just by getting the extension from the file name, but if a filename does not have an extension, is there an API call that would give me the file's type?
You cannot do this. Once the document is uploaded to DocuSign, it's always converted into a PDF. The original is not stored anywhere. You can have code that uses custom fields to store this information, but other than that - you would have to use the file name and the extension in there.
We want to send dynamically generated custom PDF documents to users for e-signature via email from DocuSign API, and get their signature back on the PDFs.
The length of the dynamic PDF will vary from a user to user. Can we place the signature field at the bottom of PDF no matter how long it is? It can be from 2 to 10 pages long.
Is this possible with DocuSign to send dynamically generated custom PDF for e-signature i.e when user open the document he/she should see the pdf that we will pass dynamically via API?
Also, what will be the PDF size limitations? I believe it is 25 MB?
Can we have flexibility in positioning the signature field based on the length of pdf? I believe there is a way to place field based on text, but how is this done with API?
We would be using both PHP SDK or C# SDK. Can you help us with any sample/example code for these SDKs?
The length of the dynamic PDF will vary from a user to user. Can we place the signature field at the bottom of PDF no matter how long it is?
Yes, use "Auto-place" positioning--also known as "Anchor Text" positioning for the Signer tabs/fields and other DocuSign fields that you add to the page. See the docs.
Is it possible with DocuSign to send dynamically generated custom PDF for e-signature i.e when user open the document he/she should see the pdf that we will pass dynamically via API?
Essentially, yes. Your app should dynamically generate the PDF for a signer, then use the DocuSign Envelopes::create call to send the signing request, including the PDF you just created.
Also, what will be the PDF size limitations? I believe it is 25 MB?
Generally speaking, that is the limit. If you start getting close to it, there are additional details to be considered. Ask another question if your PDFs are going to be that large.
Can we have flexibility in positioning the signature field based on the length of pdf? I believe there is a way to place field based on text, but how is this done with API?
You add unique "anchor" text to the documents such as /sig1/, then, where ever that text appears, a DocuSign field will be added. See the Auto-position docs mentioned above. Because you don't want the signer to see the "/sig1/" text, the trick is to have its text color be white. That way, on a white background, it won't be visible.
We would be using both PHP SDK or C# SDK. Can you help us with any sample/example code for these SDKs?
Some example code is available now on the DevCenter. We will be adding more in the future, but not for a couple of months.
The Problem
I recieved a pdf file at work which I then printed. In the pdf file there were several optional fields where one could enter information such as "place of birth" etc. If I open the pdf file on my computer, I can see a set of input information A (a travel request with dates from this year 2017).
If I print the pdf on the local printer, the printed document contains a set of information B which for example contained travel request dates from 2015.
This information was not visible when opening the file on my computer.
I have been able to reproduce the error multiple times.
Why is this a problem?
It seems that previous entries into the pdf were yet somehow stored in the pdf contrary to what was visible when opening the pdf. When printing, the printer seems to access only the oldest entries and prints those.
This is a potential breach regarding data privacy and security since the pdf file seems to save all previous entries without anyone knowing.
Especially at work, some of these pdfs contains bank account information and other identity related information.
The Question
Did anyone experience a simliar issue or knows how to delete the invisible old information yet stored in the pdf?
UPDATE1: I could not reproduce the error on other printers. It seems this error is caused by the specific printer. Yet the information must be present in the PDF file, which is the specific cause of my question.
UPDATE2: Using the information from the accepted answer, I used the program "PDF CHAIN" and selected the option "drop XFA from document". I then saved the manipulated document again and printed it on the same printer.
Finally, the correct information was printed.
At a guess (and that's all it is without being able to see the original file) the PDF contains optional content or annotations which contain different field data for Print and Screen.
If you open the file using a PDF consumer (eg Acrobat) then what you see is the 'screen' result. Depending on the consumer you are using it may then either send the screen data to the printer, or substitute with the 'Print' data.
The printer you note as being a problem is capable of direct PDF printing, you haven't stated if that's how you are printing the PDF file, or whether you are using an application, nor whether the other printers are PDF capable or not.
My guess is that there is a different decision being made somewhere in the 2 print paths as to which is the 'correct' information to print.
Note that this does not mean that the PDF 'seems to save all previous entries without anyone knowing'; that's not really possible with a PDF file.
A malicious PDF processing application could do so, by adding comments to the PDF file, but only that application would be able to retrieve it.
But it is possible to have multiple entries of different types for different purposes, and if they aren't the same (because of the tool used to edit the file) then you can get strange results like this.
Note that if this is a problem for you then you probably shouldn't be using PDF, but you can mitigate the issue by digitally signing your documents. Signed PDF files include means (secure cryptographic hash) for verifying that the document has not been tampered with . Of course, you can't then edit the PDF file without re-signing it.
Oh, one other possibility would be that the PDF was actually an XFA form; its possible to have part of the document be a valid PDF which prints 'something' when a PDF consumer can't handle an XFA form, but that need bear no relation to what you see when you use an XFA processor.
My money's on optional content, AcroForm fields, or annotations where the Print data is different from the Screen data though.
If I'm using an anchor for signer initials, and I want it to appear on every single page. Can I do this with DocuSign using an HTML document?
It's easier for us to create and maintain HTML templates to add to envelopes than it is Word docs or PDFs. However none of the methods of trying to get an HTML repeating footer (the footer prints on every page) seem to work. Is it possible?
DocuSign will accept a wide variety of document types, but upon import into the DocuSign system, all documents are converted to PDF format. So, while it's feasible to supply an HTML file to DocuSign, don't expect DocuSign to interpret/process any of the HTML code that your HTML file contains, because as soon as it's imported into DocuSign it's no longer an HTML file -- it's just plain text.
So, if you want to use anchor text for placement of signer initials at the bottom of each page, then the document you upload to DocuSign (regardless of file format) will need to explicitly contain that anchor text string at the bottom of each page.
I wish to digitally sign my image collection which consists of JPG , TIFF , BMP , SWf , Fla files.
My question is how to digitally sign these images? If I sign JPG or Tiff , whether signature will get attached to these files (as it happens in document files like PDF or MS word etc)? If so where it get store in file metadata fields , or remain outside? Can i extract signature data?
Please note I wish to sign these images Individually and do not want to get converted into any other format like PDF. Also I donot wish to sign it using email client.
In general those formats were not designed with signing in mind, so your best option is to create a detached signature and keep it near the file. An alternative is to use wrapping signature but then other software won't be able to display the image until you remove the wrapper.
Storing the signature in metadata can be possible for some formats but what applications would be able to handle this?
I know it has been a long time, but you might want to look into steganography. Metadata can be extracted and removed from files. Steganography will allow you to embed digital signatures(encrypted phrases) in a way that is almost only detectable using statistical analysis.
You can also create a mime container which will contain the original image and a detached signature.
Attached signatures are only useful for specific apps, as they are not standard.
Try answering the posters question folks, and not giving another unneeded and unwanted opinion, it's way to common these days in my humble opinion.
Obviously what the poster asked for is to use a signature to copyright his works, so you need to sign the image, period, And a method to do so.
So let's see... grab Gimp or Photoshop. Get your image and create a new layer with transparent background. write in a signature with your mouse or digital pen in an area near the bottom right edge. Choose merge layers and flatten image. Seems like that would do it.