This topic contains 3 replies, has 2 voices, and was last updated by  Duo_Liang 2 weeks, 4 days ago.

  • Author
    Posts
  • Participant
    anusha
    Newbie
    Member since: 01.05.2019
    Number of posts: 2

    Hi,

    I need a help in the below scenario please revert back to my doubt as soon as possible.

    I have a PDF file which as two text field with id {{esl:Signer1:Capture}}. I am trying to change these field to a signature field using the below code
    .withSignature(SignatureBuilder.captureFor(“Jhonson@gmail.com”).withName(“{{esl:Signer1:Capture}}”).withPositionExtracted()) while creating a package. In this case, it is updating the one field to signature field where the other one doesn’t. Please help me with the better solution and let me know if you need further details.

    Thanks,
    Anusha.

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 828

    Score

    0

    Hi Anusha,

    The feature you are using is called “Position Extraction”(guide here) which uses PDF form’s property name as an indicator to create fields, but this feature would only take one recognized PDF form. So in order to resolve the issue, you could name PDF forms in different names.

    And BTW, the naming convention of your PDF forms “{{esl:Signer1:Capture}}” was the syntax of our Text Tags feature (guide here), so is there any specific reason that you didn’t directly use this feature but Position Extraction instead? Because Text Tags feature allows converting all recognized tags into OneSpan Sign fields.

    Hope this could help!
    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist
    Participant
    anusha
    Newbie
    Member since: 01.05.2019
    Number of posts: 2

    Score

    0

    Hi Duo Liang,

    We had a document with label “{{esl:Signer1:Capture}}” when the user tries to download the document the same label appears in the flattened pdf. So we wanted to have the signature field as text box with id “{{esl:Signer1:Capture}}” and while connecting to onespan the text box needs to be replaced to signature field. Is their a better way to implement this scenario.

    Thanks,
    Anusha.

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 828

    Score

    0

    Hi Anusha,

    Could you share the document where “the same label {{esl:Signer1:Capture}} appears in the flattened pdf” to developer@esignlive.com so that I can have a closer look at the issue? And please remove the sensitive information.

    Because ideally, it won’t happen in Text Tags feature cause all tags will be removed and be replaced by OneSpan Sign fields. And this is the recommended way for your scenario.

    Alternatively, as I mentioned above, as long as you use different PDF form names (don’t have to follow esl:{SignerName}:{fieldType} convention, you can simplify the names like “Capture1”, “Capture2”) and call the code snippet twice, they will be replaced by capture signatures.

    ...
    .withSignature(SignatureBuilder.captureFor(“Jhonson@gmail.com”).withName(“Capture1”).withPositionExtracted())
    .withSignature(SignatureBuilder.captureFor(“Jhonson@gmail.com”).withName(“Capture2”).withPositionExtracted())
    ...

    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist

You must be logged in to reply to this topic.