Sudipta

Not apply the same signature to the next signing block

0 votes
Hello If a document has multiple signature blocks, on clicking the first signing block a popup appears to capture the signature and from the next signature block onwards it applies the captured signature to the signing block. Can we stop the eSignLive document to apply the first signature to the remaining blocks? I want to be able to scribble my signature for all the blocks and not apply the first one to all of them. Thanks Sudipta

Reply to: Not apply the same signature to the next signing block

0 votes
Hello Sudipta, Yes, you can. Please contact [email protected] to set enforce capture on your account. This will require each signature be captured vs turning all but the first into click-to-sign (with original capture data copied).

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: Not apply the same signature to the next signing block

0 votes
Thanks for the information. By any chance, can this setting be defined at the time of package creation from API or SDK? -Sudipta

Reply to: Not apply the same signature to the next signing block

0 votes
From the API, this is part of the settings object in the payload and therefore should be able to be set on a transaction by transaction basis:
"settings":{
     "ceremony":{
          "enforceCaptureSignature": true
     }
}
I will have to look into whether this was added to the SDK, yet. I will let you know. If you figure it out before I post back, please update this thread. :) Thank you!

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: Not apply the same signature to the next signing block

0 votes
In a blog dated Sept 13, 2017, it says that this change is not yet part of SDK https://www.esignlive.com/blog/esignlive-developer-community-24-09-2017/ Can you help us checking if this is part of the SDK now or is this change in pipeline?

Reply to: Not apply the same signature to the next signing block

0 votes
I just looked in the latest SDK (11.13) and I do not see this setting on the package settings. Until it is available, you could create your transaction in DRAFT mode and then do a REST call to update the package settings before sending the transaction. I will see if it is on the plan to add this setting to the SDKs, in the roadmap and report back. This will likely be tomorrow before I hear anything as Montreal (eSignLive main office) is on holiday, today.

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: Not apply the same signature to the next signing block

0 votes
Hello Thanks for the clarification. When I tried to update the 'enforceCaptureSignature' field of the package using the PUT API URL : PUT https://apps.esignlive.com/api/packages/O-vXz8y_nZpx87g4Vfgnw4b4ZA4= Request Body: { "settings": { "ceremony": { "enforceCaptureSignature": true } } } I get 403 forbidden error: { "messageKey": "error.forbidden.cannotEditDeletePkg", "technical": "package: O-vXz8y_nZpx87g4Vfgnw4b4ZA4= cannot be edited.", "message": "Cannot edit or delete package.", "code": 403, "name": "Access Denied" } I am using the same key that I use to create the package. Am I doing anything wrong? I use .withStatus(PackageStatus.DRAFT) to set the package as a DRAFT while creation. Also tried eslClient.changePackageStatusToDraft(packageId) to set it to DRAFT state.

Reply to: Not apply the same signature to the next signing block

0 votes
Let me test it out. I will also let you know when I hear about this feature at a package level. Initially, as I first answered, I thought it was only available from the account level, until I saw the property in the JSON and mentioned it to you. Stay tuned.

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: Not apply the same signature to the next signing block

0 votes
Can you please share an update on this?

Reply to: Not apply the same signature to the next signing block

0 votes
Sorry for the delay. I was out of my office, at HQ, this week and was in meetings on Wednesday and travel all day Thursday. We've tested from the API level and it seems to work. This is not working for you? Also confirmed, this is not in the SDK, yet, but will hopefully be added in a coming release.

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: Not apply the same signature to the next signing block

0 votes
I am getting a 403 when I do a PUT on the https://apps.esignlive.com/api/packages/O-vXz8y_nZpx87g4Vfgnw4b4ZA4= I get 403 forbidden error: { “messageKey”: “error.forbidden.cannotEditDeletePkg”, “technical”: “package: O-vXz8y_nZpx87g4Vfgnw4b4ZA4= cannot be edited.”, “message”: “Cannot edit or delete package.”, “code”: 403, “name”: “Access Denied” } I am using the same key used for creation of the package. Can you give me a sample of the API requests which succeeded for you so that I can compare and check if I did anything incorrect?

Reply to: Not apply the same signature to the next signing block

0 votes
Is the transaction in SENT status when you're trying to update it? If so, it'll need to be in DRAFT mode. I would assume this would be a setting you would set at create time, in real practice, so, editing a transaction wouldn't be the normal scenario. Unless I'm wrong on that, for your actual workflow.

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: Not apply the same signature to the next signing block

0 votes
Thanks for the information. It worked for me! I had been trying to use the PUT API after SENDing the document. I changed my code and did the PUT before sending the doc. It works for me now. Can you please give me an idea on when this feature might be part of SDK?

Reply to: Not apply the same signature to the next signing block

0 votes
We are experiencing unresponsiveness in the SDK method calls and API calls as well. Are the eSignLive services down?

Reply to: Not apply the same signature to the next signing block

0 votes
For the first question, I will talk to the PM of the product and ask. As for the service being up or down, the best place to find that information is in the Trust Center. I believe there was a short period of outage right around the time you posted, but all should be good, now.

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off