Hello,

In this question I am not looking for any technical details or answers to how to integrate as I am fairly comfortable with our ability to do what is needed.  Instead, I am just looking for someone who might have done this before or someone from OneSpan to look over what we want to do and tell me if the OneSpan Sign SaaS solution will allow this or not and tell us if there will be unforeseen constraints going about it this way.

Background

Hello Onespan,

I am stuck with the issue for a while and decided to post something here.

 

I am currently using two documents for signing.

One document is in .pdf format and this works fine.

The second document is in .docx because I need to use mergefield to fill blanks. And then, My program converts it to PDF  then use it in Onespan.

 

The first document has no problem showing signed fields in browsers like Chrome and Edge.

(Without touching any configuration)

Hi excuse my ignorance as I am migrating from Adobe Sign and

trying to use the text tags to trigger Signer1 fields in my uploaded document.

I have tried a few iterations of trying to get a Signer1 Signature field recognized after i have uploaded

a pdf with the following tag:

{{esl:Signer1:signature}}

Upon upload to eSignLive when I review the tags in the document there is no Signer1 Signature field showing.

Is my tag wrong? Is this the normal behavior?

 

Thanks for your help