Account
I am a
Developer
Product(s)
Earned badges
Achievement: Latest Unlocked
Preferences
Replies
Topics Started
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
Thursday, April 19, 2018 at 05:14amMy 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?
Reply to: Text Anchors with a reverse occurrence index
Tuesday, February 20, 2018 at 08:56amHi, I wanted to follow up with you regarding the enhancement request that you mentioned you created.
Having this feature would be very helpful for our business.
Reply to: Text Anchors don't work after a document has been added to a package
Tuesday, January 9, 2018 at 05:03amThanks 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
Tuesday, January 9, 2018 at 07:18amI 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"
Reply to: Signature Name is not being persisted
Tuesday, February 20, 2018 at 09:00amHi, I wanted to follow up about this bug to see if it has been fixed or if there is a timeline on when this will be fixed.
Thanks,
David
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 | 6 years ago | 39 |  |
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 2 months ago | 9 | |
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 3 months ago | 25 | |
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 2 months ago | 30 | |
In the latest SDK, there were additional signing ceremony customization's added. Specifically, I'm noticing WithOptOutOther and WithDeclineOther.
|
1 | 6 years 4 months ago | 4 | |
Subscriptions Release Notes
This user is not subscribed to any release notes.