ADA transaction failed when confirm

OSS uses position extraction for ADA transaction, and use document extraction for non-ADA transaction.  when the signer launched the signing ceremony, both ADA and non-ADA are available. and if create package using document extraction, if signer enabled ADA and sign in ADA mode, it's not work. what's the use case from OSS for this scenario? 

Hi Cindy,

First regarding the error you saw. I believe it's because when designing the PDF, you need to use an Adobe Signature Field instead of the regular PDF form field. (And don't forget to tag the signature form)

Talking about the ADA vs non-ADA transaction, position extraction vs document extraction. There's a fact that once you've created the transaction, you can't change the ADA setting. That's to say you can't really use one PDF for both ADA and non-ADA use cases. That's why I would suggest you to use two PDF versions:

- one for non-ADA usage where you used document extraction and the signature is represented by PDF form field

- one for ADA usage where the PDF is properly tagged, and the signature field is represented by Adobe Signature Field. (The form field names can be simplified since the document extraction syntax won't work here)

Duo

Hi Duo, 

thanks for the information. as I am using the document which you shared with me earlier and the payload as attached for testing. the signer is able to sign when ADA mode is disabled, but when ADA mode is enabled, signer got error message when click "Done" button after apply the signature in the signature box. 

any idea?

Also regarding ADA enabled vs disabled, I understand your point, but from my idea, once I created the package aiming for ADA, so during signing ceremony, it showed show the signing in ADA mode immediately instead to ask signer to toggle enable ADA, what do you think?

thanks,

Cindy

Hi Cindy,

For this PDF and payload (TestDocument_ADA.pdf + OSS_ADA_Payload.txt), the error is introduced in release 11.49 where the auto field (signing date in this case) breaks the ADA signing. You can work it around if you temporarily remove the signing date field in your code. An R&D ticket has already been opened to fix this.

And still, please be aware that this is different from the issue we discussed above, and you will still need an Adobe Signature field for the signature.

In terms of turning on ADA mode by default, if you are building the signing link with either of below two formulas, adding a parameter "isAda=true" should work:
https://sandbox.esignlive.com/access?sessionToken=M2U0NzJlZTEtOTUwYy00ZmIwLWIwZDktOTY2Y2Q3MGQ2NjZk&isAda=true

https://sandbox.esignlive.com/authentication?target=https://sandbox.esignlive.com/transaction/SDzHYNEpX1dqJ_r53Y41Sd-Oodk=/sign&loginToken=YlZpT1VVenRaWGZJMHNzdlV3V1hsbEtyQmk4WlZxelk0dktibk1SdlFEYkV2M21vY0RVY0VtbnMwV1JWTUMyKzJPak4rNGhSSTNGK3hrVW5HemUyUEZKTWhDcThDYTJmNXVITFNtU0cydDFQN2dDSWFsWFU0Q0FDeDdmM3c5R3NXWEZYVGxWeGJFUm9RMlY1VTBaMU5FcE1lRzFSWVc1b1VqVm5ZVE5CT1ZOeFpYTlBaVUkxYjBsVFIwWldhVzFRYTBFMVREVlFVV1JYZG10YVFVYzJlUnhIREJ0dTE0K3REK3ZCRU8wV1JMckY5MlpVZStzTkcwTEY4QmdYeHdicA==&isAda=true

Duo

Hi Duo, 

could you please share the R&D ticket number so I can do the followup? 

also for the signing URL, since we do remote signing, and signing URL is embedded in the email templates, how to update it with adding Ada=true

Hi Duo,

when the signer signed the document in ADA mode, when reviewing the document after confirm the signature, there is "image signature without text" in the signature box instead of showing real signatures. I attached the screen. what does it mean?

thanks,

Cindy

Hi Cindy,

(1)For "image signature without text" in the signature box

I am assuming that your package has capture text hidden by default:

 "settings": {
    "ceremony": {
      "hideCaptureText": true
    }
  }

Or

 .withSettings(DocumentPackageSettingsBuilder.newDocumentPackageSettings()   
                  .withoutCaptureText()
 )

If you had the capture text turned on, the signature typically says "e-SIGNed by {firstName} {lastName}"

(2) R&D ticket number for auto field breaks ADA signing: PB-89668

(3) To launch ADA signing mode by default

I have confirmed internally that OSS currently doesn't have the option to append "?Ada=true" parameter to signing url ("Go to Document" link in invitation email) for ADA transactions. Also, if we will hit an error when launching non-ADA transactions with this parameter, hence to hardcode value in the email template won't work this in case. If you preferred, I can fill in an Enhancement Request on behalf of your organization to have either a package setting or a backoffice / account level setting to determine whether to add this parameter in the signing URL.

Duo

Hi Duo,

for #1, yes, the sample has capture signature with "hideCaptureText" = true, so "image signature without text" in the signature box is expected?

for #3, I will discuss with our internal team if needed, we will submit ER request to our CSR.

thanks,

Cindy

Hi Duo,

Is there an estimation on when this will be fixed?

(2) R&D ticket number for auto field breaks ADA signing: PB-89668

Thanks,

Kabir