Update document content & signers reatining the already obtained signature

Hi Anu,

Please be aware that OneSpan Sign has below limitations:

(1) Once a document has been partially signed, OneSpan Sign doesn't allows user to update the document content or redesign the metadata.

(2) For recipients who have already signed, you can't update their email, first / last names, title and company information.

Based on above, it's impossible to "update the document content (bytes) without losing the already obtained signatures from Signer A" and the solution is exactly like you mentioned, to "delete the document A although it has been signed by Signer A, and re-add an updated version of the document"

For signing status, it's supposed to behave like this:

(1)when package first get sent, the signing status of signer A should be:
DRAFT --> SIGNING_PENDING

(2)when signer A signed Document A, because he/she has signed all signatures assigned to him/her, therefore the signing status should be

SIGNING_PENDING --> SIGNING_COMPLETE

(3)when you moved the package to DRAFT, deleted the Document A, added a new Document B and assigned new signatures to signer A, the signing status should be:
SIGNING_COMPLETE --> DRAFT

(4)send package the second time, the signing status:
DRAFT --> SIGNING_PENDING

So it's expected that signer A will receive the email again, but shouldn't in the status of "SINGING_COMPLETE". If you could reproduce the inconsistence with the same flow, we should continue to investigate on it.

Duo

Hi Duo,

Thank you for your inputs.

I think the case of Signing_Complete for Signer was before the transaction status was changed to draft. And once the document was re-added and package sent again for signing, Signer's signing status is SIGBING_PENDING. 

As soon as the package status is changed to draft, the Signing status of all the signer's change to INACTIVE not DRAFT. Also once package is in draft, even the signed Signer's status says INACTIVE and not SIGNING_COMPLETE