We have registered Callback Event Notification on OneSpan Sign Web UI and Key is getting gernerated correctly. However, I am receiving below error on email as OneSpan Sign Sadnbox access is assigned to me only.
We are able to generate the URL for NDA and storing on Opportunity object in Salesforce and we are receiving below errors -
We're trying to generate the package using template. Templates are created in sandbox.esignlive.com. While generating the package we're receiving below exception, OneSpanRESTAPIHelper.OneSpanRestAPIHelperException: Error updating package with OneSpan: 400 - Bad Request - {"messageKey":"error.validation.packageActivation.unassignedRole","message":"There is a role with no signer.","code":400,"name":"Validation Error"}
We're executing below code,
OneSpanSDK sdk = new OneSpanSDK();
Is it possible to pass attachments to eOriginal?
Hi all,
What does the following error message mean when trying to pass through a Salesforce attachment to OneSpan?
Error creating OneSpan package with documents: 520 - null - error code: 520
I've since called our method used to do this process manually, and it generated fine (without the attachment being modified in any way).
We did have roughly 10K packages generated within a few hours, is this what could have caused it?
Thanks,
Cameron
Are we able to merge data onto a document and also set it as "accept only"?
I am following this blog post but wondering if we can stamp the fields on the document with values too: https://www.onespan.com/blog/onespan-sign-release-1150-accept-only-rework
We need to push our signed documents into an eOriginal vault. The instructions say to push it through a "data" field in the API.
Question #1: Location and Procedure
There are data fields in the root and in a few different. I'm assuming that this data is going in the root. The sdk also doesn't seem to support the root data field, so I'm assuming I'm going to have to send that using a manual post.
Question #2: Formatting
The manual API post looks to be something like:
~~~
We are working on creating Onespan transactions in Salesforce and have written out some Apex Trigger code to assist with the process. In order to use it in Production, we will need to write an apex test class that cover the code itself. In doing this, we are facing the below error when we try to insert, in Salesforce, a Onespan Transaction record. We are able to do the API callouts properly and they do get created on the OneSpan side. Has anyone received this error before or know what we need to do to not run into it?
Error:
Is it possible to create 2 optional signature blocks in a document that are intended for 'additional signers' that have not been defined as a signer in the package?
We've got our main signer, and we want to give them the option to bring in two more people to sign if they need to. We'd also like to have a way to collect the names of these extra signers using text fields. We've been trying to figure out how to add those two signature spots, but we're having some trouble.
Hi all,
How can I make a checkbox field required so that a client must mark this as TRUE (as well as doing the normal digital signature)?
Thanks in advance
I have the code working that sets the "sender" when the package is not in-person. But this code doesn't seem to work with in-person. All the in-person packages shows me (account owner) as the owner even when I set a different user as the sender.
According to the package information, the sender information is not there and I'm listed as owner. Is there a way to customize the owner?