Account


Earned badges

Achievement: Latest Unlocked

Topic Started

Topics
Hi, I've come across a situation where a signers signing status for a particular document does not get updated when the document is declined. It can be reproduced as follows: 1.
I am seeing a possible bug where I am creating a package with 1 document, 1 signer, and 1 signature. When creating the package, I give the signature a unique name using the
.WithName(string sign
I am seeing a bug where the following occurs: 1. I create a package with 1 document and 1 signature placed using text anchors. 2.
Currently when using a text anchor to place a field or signature block, we can specify the occurrence index (i.e. 0 = use the first occurrence of the specified text.
In the latest SDK, there were additional signing ceremony customization's added. Specifically, I'm noticing WithOptOutOther and WithDeclineOther.

Replies Created

Reply to: Optional Signers or Opt-Out Functionality

2 votes
My company also requires this functionality. When we demo'd our application with eSignLive functionality integrated into it, our clients first question was about having someone else take over the signing responsibility. This means that we need to add/remove signers after a document has been partially signed. Is this still in the road map?

0 votes
Thanks for the clarification. I did not notice this when I was reading through the documentation. Is there a reason why this was chosen as a design decision? My end goal was to provide a feature to change a signer grammatically. This would include 1. Removing the original signer 2. Adding a new signer 3. Adding all new signatures and fields to replace the original signer. 4. Give the new signer fields default values based in dynamic data hosted in our back end database I suppose I can look at the absolute positioning of the original signature block and fields and then just duplicate those settings to create the new signature block and fields.... but that solution isn't as clean as using text anchors after document upload. Is this a feature that is planned for the future?

Reply to: Signature Name is not being persisted

0 votes
I believe I can use your suggestion and use the SignatureId field instead. My question to you is as follows (as I'm worried it might cause issues) Can we re-use the same signatureId for signatures across different documents in different packages? e.i. Package1 >Document1 >Signature1 with Id "myId" Package2 >Document1 >Signature1 with Id "myId"

Subscriptions

Topics Replies Freshness Views Users
Hi, I've come across a situation where a signers signing status for a particular document does not get updated when the document is declined. It can be reproduced as follows: 1.
5 5 years 10 months ago 37
Profile picture for user harishaidary
I am seeing a possible bug where I am creating a package with 1 document, 1 signer, and 1 signature. When creating the package, I give the signature a unique name using the
.WithName(string sign
4 6 years ago 9
Profile picture for user harishaidary
I am seeing a bug where the following occurs: 1. I create a package with 1 document and 1 signature placed using text anchors. 2.
4 6 years 1 month ago 23
Profile picture for user harishaidary
Currently when using a text anchor to place a field or signature block, we can specify the occurrence index (i.e. 0 = use the first occurrence of the specified text.
2 6 years ago 27
Profile picture for user harishaidary
In the latest SDK, there were additional signing ceremony customization's added. Specifically, I'm noticing WithOptOutOther and WithDeclineOther.
1 6 years 2 months ago 4
Profile picture for user harishaidary

Code Share

This user has not submitted any code shares.

Subscriptions Release Notes

This user is not subscribed to any release notes.