I am working on a solution to create a package containing a single document.
When I use a .pdf file, this works fine - the document is sent; a signing URL is generated and I can sign.
When I try to use a .docx file, I get a HTTP 400.
For this form, we are seeing an unusual behavior. Prior to signing, the values in a label field are appearing in a different format than after signature. The line breaks are not being recognized before signing.
See the attached images. Our preference is the after signing format.
This is generated via the Apex SDK.
Any thoughts on how to prevent this?
We're trying to implement OneSpan Sign, but in the process of using Apex SDK, we noticed that Callback Event Notifications are not getting created for the transaction. If we create the transaction manually in Salesforce, event notifications are created for the transaction. Is there a set of requirements that need to be met in order for Callback Notifications to be turned on for a Transaction?
Is it possible to download the signed document and evidence summary PDF as a single PDF with the apex SDK? Right now we get each file separately.
We noticed this morning that when a packageID contains _x something in the Apex SDK is removing it from the string. We are passing in:
packageId = '6h_xtu2OH3w-7q9B1Xww0ztuIm0="
OneSpanAPIObjects.Package_x pkg = sdk.getPackage(packageId);
pkg.trashed = true;
sdk.updatePackage(pkg, packageId);
HI Team,
How can we allow a particular signer to upload a signature file into the agreement?
I know how to do it from UI but need to do it using salesforce apex code. Right now we are just adding the role as below.
Could I get someone to look at this package and help me understand why the signer got "Unauthorized Access: Failed to validate token"? The method that was used to generate the URL is run several times per day successfully but this one failed.
Package ID: Snoq9zzWq5RvRsTPJ3J2ahIDPBk=
We had one other package also fail with the same error.
I am trying to submit a merged document and consistently getting this error. The document is passing Adobe Acrobat Preflight. Is there any additional insight into probable causes of this: error.validation.createProcess.missingData?
I would be happy to share the doc via an alternate method than this forum.
We have a use case for the sender to attach an additional PDF document to the form in the package. For context, our implementation has a library of forms that our users can select from with pre-defined merge fields and signer blocks. We do not use the designer tool. We use a combination of apex, lwc, and flow to create the onespan package and we are envisioning allowing the user to upload a PDF the would appear as part of the signing ceremony.
Our imaging team is complaining about the OneSpan documents that they are receiving:
"Is there any way to disable the secure feature of Saleforce’s e-Signed documents?
We have been experiencing an uptick in issues with PDFs being rejected. Our investigation found that end users are using OneSpan e-sign capabilities via Salesforce to get the documents signed. When the documents are attached they come in as secured documents which cannot be uploaded because they fail our validation check."