serenapotts3's account

See our download tool https://community.onespan.com/documentation/onespan-sign/codeshare/onespan-sign-package-export-download-tool which allows downloading for a month period. If you need for longer you can use this version which does for a year. https://community.onespan.com/sites/default/files/codeshare/OSS - Package Export  %26 Download Tool - v1.1.5 - 1 year limit.jar_.zip 

it depends on if the event is generated by a signer of sender actions. It will have the corresponding sender or signer id then in the property.

For example:

• sender triggered events such as  PACKAGE_CREATE, PACKAGE_ACTIVATE, PACKAGE_DEACTIVATE etc will have the sender id.
• signer triggered events such as DOCUMENT_SIGNED, SIGNER_COMPLETE etc will have the signer id.
• PACKAGE_COMPLETE in the case of multiple signers will have the signer id of the last signer to sign.

Would it be possible for the Completed package list in this tool where you choose which packages to export, to show a table with information similar to in the transaction listing in the web UI shown below? For transactions sent with bulk send all transactions have the same name so it is very hard to differentiate between transactions without referring back to the transaction id which is not very user friendly to use to identify.

When you use the tool to copy templates from a sandbox to production account, the SANDBOX watermark appeared to be on the documents. Is there anyway to remove this? Or do the layouts need to be saved to maintain the fields and the documents need to be deleted and uploaded to the template again?

When you use the tool to copy templates from a sandbox to production account, the SANDBOX watermark appeared to be on the documents. Is there anyway to remove this? Or do the layouts need to be saved to maintain the fields and the documents need to be deleted and uploaded to the template again?