Add Signed OneSpan Document to another package

Hi Ranjan,

Thanks for your post!

Because uploaded documents will be flattened by document engine first, therefore I won't think it's currently feasible to re-upload a signed document and still keep the original active signature(s).

As a workaround, I think you can specify the signatures for internal signers as optional, so that at the point when client signed the document, you will receive a "PACKAGE_READY_FOR_COMPLETE" notification. You can treat the transaction as a completed one, for example to download the signed document along with the evidence summary. While the transaction status won't be COMPLETED until all the optional signatures have been signed, or the sender mark complete the transaction.

Duo

Hi Duo,

Thank you for your answer. 
The problem is that we do not know which internal employees will be signing the document later. This will be done when the requirement arises. Is there a workaround this?

Regards,

Ranjan

Hi Ranjan,

This is kind of general that if a signer never started to sign, the transaction owner still had the chance to edit the signer information. Therefore you can put a general email for the internal signer first and only edit it when the requirement arose.

Duo

Hi Duo,

Last Question,

How long will be a package available if it is not completed? Our scenario is to use the document over multiple internal employees for multiple time period, so there will always be a signer that will not sign the document according to your proposed solution.

Regards,

Ranjan

Hi Ranjan,

You can refer to the Data Retention Guide for more detailed information. Depending on the type of your account, the default retention interval for Incomplete Transactions is 120 days, and if your account is with business plan, you can extend this period (up to unlimited).

Duo