"messageKey":"error.validation.verifyDocument.couldNotBeFlattened","message

Hi, getting the same error, document is correct pdf, can you please check {"messageKey":"error.validation.verifyDocument.couldNotBeFlattened","message":"Could not upload PDF document: it contains a syntax error preventing proper processing of its data.","code":400,"name":"Validation Error"}

Hi guys,

We have a case which must to star a signature process in eSignLive with a document that previously was signed by a client with a software certificate.

If we launch the process with this document and sign it, the previous signatures dissapered; anyone knows a way to keep the previous signatures and add new though eSignLive?

Thanks

 

 

Hi,

I have a scenario for a package with 1 document and 2 signers, only 1 signer required to sign the document.

when this package sent , both of the signers received the activate email (1 signer for signing, and another signer just review - no  signature required. 

then I change the package to DRAFT and Re-send, at this moment, only 1 signer which need to sign receive the activate email, but not the 2nd signer doesn't receive the email. 

We are trying to hook up OneSpan with LaserPro and have the documentation to make the connection but no instructions on how it works once completed. I understand that LaserPro will export the docs for eSign but does that then open up in OneSpan. We need the ability to add additional docs to the package (not found in LaserPro) before sending to the client - trying to solve for this scenario.

Hi 

We are using onespan integration in Guidewire 8.0.7 version and I was able to create the package in my local environment . we promoted our code to the one of testing environment. When we click save draft package button on the onespanpackagepopupscreen we are getting the NoClassDefFoundError: gw/accelerators/onespan/OneSpanJSONUtils exception. We tried different ways to resolve this issue but none of them worked. We really have no clue why this class is not being able to recognized by the compiler at runtime. 

 

This is what we are seeing - please let us know if it is expected.

The Document signed event is only sent when a signer has signed all his blocks on a document. Signing only one of multiple blocks does not generate the event. If the signer has started signing but not completed a document, OneSpan is reporting his status as SIGNING_PENDING.