Sharankrishna's account

Can we have custom names instead of Signer.Capture1, Signer.Capture2? Something like Signature1 and Signature2, but still do mobile capture.

Hi Liang, But I'm am able to apply "Document Extraction" method for Mobile Capture if I have the naming convention as [Signer.Capture1]. Signing in mobile, captures the signature against the PDF text field which has the field name as [Signer.Capture1]. If I have another field as [Signer.Catpure2], then the same signature gets affixed which was populated in [Signer.Capture1] field. My question was around why do we need enforceCaptureSignature method to be called when Document Extraction works for Mobile Capture, where it is able to copy the same Signer's signature in multiple places in the document. Is there anything extra that enforceCaptureSignature method does?

Hi Liang, Is there a reason why we would have to increment the last number in Document Extraction method, that is [Signer.Capture1] , [Signer.Capture2]? Suppose say if we have multiple places in the document where a Signer's signature is required then we should ensure the numbers are incremented correctly. Is there a way where we name the PDF signature fields with the same name (i.e two fields having the same PDF field name) so that signing in one field populates the same signature across all the PDF fields?

Thanks Liang for your prompt reply. It makes sense. Let us know once this feature is available.

Hi Liang, When we click on the popup which says “Please click OK to confirm your signatures to this document or click Cancel to review it again before submission” On clicking of Cancel still retains the old signature and doesn’t allow us to modify the signature.